Downlink control information format for ultra-reliable physical downlink control channel

ABSTRACT

Embodiments of the present disclosure describe methods, apparatuses, storage media, and systems for determining a capability of a UE to support a first downlink control information (DCI) format for Physical Downlink Shared Channel (PDSCH) reception in a downlink (DL) bandwidth part (BWP) and a second DCI format for scheduling uplink (UL) grants for physical uplink shared channel (PUSCH) transmission in a UL bandwidth part (BWP), where the first DCI format is different from DCI formats 1_0 or 1_1, and the second DCI format is different from DCI formats 0_0 or 0_1. Furthermore, a base station may determine search spaces for monitoring physical downlink control channel (PDCCH) candidates to obtain DCI formats indicated by the base station. Other embodiments may be described and claimed.

CROSS REFERENCE TO RELATED APPLICATION

The present application claims priority from U.S. Provisional PatentApplication No. 62/673,739, filed May 18, 2018, and entitled “SUPPORT OFCOMPACT DOWNLINK CONTROL INFORMATION FORMAT FOR ULTRA-RELIABLE PHYSICALDOWNLINK CONTROL CHANNEL,” and further claims priority from U.S.Provisional Patent Application No. 62/670,583, filed May 11, 2018, andentitled “SUPPORT OF COMPACT DOWNLINK CONTROL INFORMATION FORMAT FORULTRA-RELIABLE PHYSICAL DOWNLINK CONTROL CHANNEL,” the entiredisclosures of which are hereby incorporated by reference in theirentireties. The present application is a continuation-in-part of andclaims priority from U.S. patent application Ser. No. 16/277,680, filedFeb. 15, 2019, and entitled “RELIABILITY MECHANISMS FOR PHYSICALDOWNLINK CONTROL CHANNEL (PDCCH) TRANSMISSIONS IN NEW RADIO (NR)SYSTEMS,” which claims priority from U.S. Provisional Patent ApplicationNo. 62/710,411, filed Feb. 16, 2018, and entitled “Ultra-Reliable andLow Latency Physical Downlink Control Channel (PDCCH) Transmissions inNew Radio (NR) Systems,” the entire disclosures of which are herebyincorporated by references in their entireties.

FIELD

Various embodiments generally may relate to the field of wirelesscommunications.

BACKGROUND

Mobile communication has evolved significantly from early voice systemsto today's highly sophisticated integrated communication platform. Thenext generation wireless communication system, which may be referred toas 5G or new radio (NR), may provide access to information in sharing ofdata anywhere, any time by various users and applications. NR isexpected to be a unified network/system that meets vastly different andsometimes conflicting performance dimensions and services. Such diversemulti-dimensional requirements may be driven by different services andapplications. In general, NR will evolve based on 3^(rd) GenerationPartnership Project (3GPP) LTE-Advanced with additional potential newRadio Access Technologies (RATs) to improve wireless connectivitysolutions. NR may enable ubiquitous wireless connections the deliverfast and rich content in services.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments will be readily understood by the following detaileddescription in conjunction with the accompanying drawings. To facilitatethis description, like reference numerals designate like structuralelements. Embodiments are illustrated by way of example and not by wayof limitation in the figures of the accompanying drawings.

FIG. 1 illustrates a simplified network in accordance with someembodiments.

FIG. 2 illustrates results of signal to noise ratio (SNR) improvementswith respect to downlink control information (DCI) payload sizes, inaccordance with some embodiments.

FIG. 3 illustrates operation flows/algorithmic structures for a userequipment (UE) to monitor physical downlink control channel (PDCCH) toobtain the downlink control information in accordance with someembodiments.

FIG. 4 illustrates operation flows/algorithmic structures for a basestation to transmit downlink control information by physical downlinkcontrol channel (PDCCH) in accordance with some embodiments.

FIG. 5 illustrates an architecture of a system of a network inaccordance with some embodiments.

FIG. 6 illustrates an architecture of a system of a network inaccordance with some embodiments.

FIG. 7 illustrates an example of infrastructure equipment in accordancewith various embodiments.

FIG. 8 illustrates an example of a platform in accordance with variousembodiments.

FIG. 9 illustrates example components of baseband circuitry and radiofront end modules in accordance with various embodiments.

FIG. 10 illustrates example interfaces of baseband circuitry inaccordance with some embodiments.

FIG. 11 is an illustration of a control plane protocol stack inaccordance with some embodiments.

FIG. 12 is an illustration of a user plane protocol stack in accordancewith some embodiments.

FIG. 13 is a block diagram illustrating components, according to someexample embodiments, able to read instructions from a machine-readableor computer-readable medium (e.g., a non-transitory machine-readablestorage medium) and perform any one or more of the methodologiesdiscussed herein.

DETAILED DESCRIPTION

The following detailed description refers to the accompanying drawings.The same reference numbers may be used in different drawings to identifythe same or similar elements. In the following description, for purposesof explanation and not limitation, specific details are set forth suchas particular structures, architectures, interfaces, techniques, etc. inorder to provide a thorough understanding of the various aspects ofvarious embodiments. However, it will be apparent to those skilled inthe art having the benefit of the present disclosure that the variousaspects of the various embodiments may be practiced in other examplesthat depart from these specific details. In certain instances,descriptions of well-known devices, circuits, and methods are omitted soas not to obscure the description of the various embodiments withunnecessary detail.

Various operations may be described as multiple discrete actions oroperations in turn, in a manner that is most helpful in understandingthe claimed subject matter. However, the order of description should notbe construed as to imply that these operations are necessarily orderdependent. In particular, these operations may not be performed in theorder of presentation. Operations described may be performed in adifferent order than the described embodiment. Various additionaloperations may be performed and/or described operations may be omittedin additional embodiments.

For the purposes of the present disclosure, the phrases “A or B” and “Aand/or B” mean (A), (B), or (A and B). For the purposes of the presentdisclosure, the phrases “A, B, or C” and “A, B, and/or C” mean (A), (B),(C), (A and B), (A and C), (B and C), or (A, B and C).

The description may use the phrases “in an embodiment,” or “inembodiments,” which may each refer to one or more of the same ordifferent embodiments. Furthermore, the terms “comprising,” “including,”“having,” and the like, as used with respect to embodiments of thepresent disclosure, are synonymous.

The description herein of illustrated implementations, including what isdescribed in the Abstract, is not intended to be exhaustive or to limitthe present disclosure to the precise forms disclosed. While specificimplementations and examples are described herein for illustrativepurposes, a variety of alternate or equivalent embodiments orimplementations calculated to achieve the same purposes may be made inlight of the above detailed description, without departing from thescope of the present disclosure, as those skilled in the relevant artwill recognize.

FIG. 1 illustrates a simplified network 100 in accordance with someembodiments. The network 100 may include a user equipment (UE) 104communicatively coupled with an access node or a base station 108. TheUE 104 and access node or base station 108 may correspond to and besubstantially interchangeable with like-named elements described withrespect to FIGS. 5-13.

In embodiments, the network 100 may be a 5G NR system. 5G NR system usesphysical downlink control channel (PDCCH) between the UE 104 and thebase station 108 to perform physical layer control functions such asscheduling the downlink (DL) broadcast and DL/uplink (UL) unicast datatransmission, and signaling various triggers for aperiodic and periodictransmission/reception. However, various design elements of NR make NRPDCCH different from the PDCCH or enhance PDCCH (EPDCCH) designs in LTE.NR supports a large variety of frequency bands ranging from sub-GHz to100 GHz. Due to path loss and channel conditions corresponding todifferent transmission environments, it may be desirable to ensure goodcoverage for NR PDCCH transmission, particularly in mmWave bands wherenarrow beamforming is typically employed to achieve coverage. NR PDCCHsupports various frequency and spatial diversity-based transmissionschemes. NR PDCCH is also designed to support link adaptation via use ofdifferent aggregation levels (ALs). For the description below, NR PDCCHmay be simply referred to as PDCCH.

Although the resource allocation unit in NR is similar to LTE, a fewadditional units are introduced in NR in association with the controlchannels, e.g., PDCCH, as discussed in the following. Those additionalunits have not been used in the PDCCH or EPDCCH designs in LTE.

A resource element (RE), is the smallest unit of the resource grid madeup of one subcarrier in frequency domain and one OFDM symbol in timedomain. A PDCCH corresponds to a set of resource elements carrying DLcontrol information.

An NR control-channel element (CCE) includes 6 resource-element groups(REGs) where a resource-element group equals one resource block (12resource element in frequency domain) during one OFDM symbol. Variousmodulation schemes, e.g., Quadrature Phase Shift Keying (QPSK), may beused for NR PDCCH. The CCE size is designed such that at least oneUE-specific DL control information (DCI) can be transmitted within oneCCE (with code rates not close to 1).

NR REG bundles are defined to include 2, 3, or 6 REGs, and play atwo-fold role: they determine the precoder cycling granularity (whichaffects the channel estimation performance), as well as the interleavingunit for the distributed REG mapping.

An NR PDCCH candidate includes of a set of CCEs, for example, 1, 2, 4,8, or 16, corresponding to ALs 1, 2, 4, 8, 16, respectively. A controlsearch space (SS) includes of a set of NR PDCCH candidates, and closelyassociates with the AL(s), the number of decoding candidates for eachAL, and the set of CCEs for each decoding candidate. A SS in NR may beassociated with a single control resource set.

A control resource set (CORESET) is defined as a set of REGs under agiven numerology (for example, sub-carrier spacing). Particularly, inthe frequency domain, a CORESET is a set of contiguous or distributedphysical resource blocks (PRBs) configured using a 6-PRB granularity,within which the UE attempts to blindly decode the DCI. There is norestriction on the maximum number of segments for a given CORESET. Intime domain, a CORESET spans 1, 2, or 3 contiguous OFDM symbol, and theexact duration is configured to the UE by higher layer such as systeminformation (SI) or UE-specific RRC depending on whether it is commonCORESET or UE-specific CORESET. Compared to LTE PDCCH, theconfigurability of CORESETs enable efficient resource sharing between DLcontrol and shared channels, thereby allowing for efficient Layer 1signaling overhead management.

One of the factors that can impact the time-duration of a CORESET, isthe bandwidth (BW) of the corresponding carrier, such that more controlsymbols may be allowed for smaller bandwidths. For example, assuming aCORESET includes of 48 PRBs with 2 OFDM symbols, there are 16 CCEs thatcould accommodate up to two PDCCH candidates at AL 8 or a singlecandidate at AL 16. Furthermore, there can be multiple CORESETs inside asystem bandwidth, so the CORESET may not fully occupy the whole systembandwidth in frequency domain, or DL power boosting could be applied toCORESETs that occupy narrow frequency regions within the carrier BW,depending on targeted coverage. In that case, 1 or 2 OFDM symbols maynot be sufficient. One-symbol CORESET offers benefits from theperspective of latency and control overhead adjustments especially whenthere are not many UEs in the cell or when the coverage target islimited (e.g., small cell deployments). The maximum CORESET durationthat may be configured in a cell is configured implicitly via PhysicalBroadcast CHannel (PBCH).

A UE may be configured with one or more CORESETs (using UE-specific orcommon higher-layer signaling) with a maximum of three CORESETs perconfigured DL Bandwidth Part (BWP). Limiting the maximum number ofCORESETs is beneficial for enabling more practical RRC signaling andhelp enable better UE dimensioning. Note that, the schedulingflexibility may not be impacted by limiting the maximum number ofCORESETs since different monitoring occasions can be configured flexiblyeven with association to the same CORESET. Here, it is important to notethat the concept of PDCCH monitoring periodicity is defined per searchspace set and is not configured at the CORESET-level. Every configuredsearch space with a certain monitoring periodicity (in terms of slotsand starting symbols within the monitored slots) is associated with aCORESET.

In order to support ultra-reliable low-latency communication (URLLC)services which target 1 ms latency and 99.999% reliability, control andshared channels may employ advanced transmission schemes which maximizediversity and energy within a very short transmission interval. In thatsense, reliability of physical downlink control channel (PDCCH) iscritical to provide both downlink (DL) and uplink (UL) operation.Recently, support of 16 control channel elements (CCE) per decodingcandidate was agreed that brings improved coverage for the consideredenhanced mobile broadband (eMBB) use cases. However, in order toefficiently support ultra-reliable and low latency communications(URLLC) requirements, further enhancements to NR PDCCH and downlinkcontrol information (DCI) format designs are expected.

PDCCH Reliability and Coverage Enhancement Via Compact DCI Formats

A further means to improve the PDCCH reliability, coverage, and latencyperformance is by reducing the amount of DCI payload that is carried bythe PDCCH for scheduling of PDSCH or PUSCH.

FIG. 2 illustrates results of SNR improvements with respect to DCIpayload sizes. As shown in FIG. 2, there may be about 1 to 1.5 dB of SNRimprovement achieved if the DCI payload size is reduced by up to around20 bits.

Towards reducing DCI payload size, one approach may be to consider thefallback DCI formats, for example, DCI formats 0_0 and 1_0 (for PUSCHand PDSCH scheduling respectively) as a starting point, and reduce theDCI payload further by considering removal and/or bit-width reduction ofvarious DCI fields based on assumption of pre-configuration (via higherlayers) and/or some scheduling flexibility reduction. In anotherapproach, the non-fallback DCI formats may be considered as the startingpoint and various bit-fields could be removed or their bit-widthsreduced based on the assumption of pre-configuration (via higher layers)and/or some scheduling flexibility reduction. Note that, for bothoptions, new DCI formats may be defined based on the above principles.

Embodiments of this disclosure may be generally directed to mechanismsrelated to optimization and re-interpretation of the fields in theexisting NR DCI formats for URLLC applications, as well as theintroduction of a new compact or size-matched DCI format or a newsize-matched DCI format for DL and UL scheduling. Embodiments mayinclude a potential new compact or size-matched DCI format or a newsize-matched DCI format that may be referred to as DCI format 0_2 and1_2 for UL and DL scheduling respectively. Specifically, embodimentsherein may present methods of configuration of the new DCI format forPDCCH monitoring and adaptation to certain Layer1 signaling approachescompared to the use of the DCI formats 0_0/0_1 and 1_0/1_1 for DL and ULscheduling respectively.

In embodiments, means are presented for facilitating operation withPDCCH with high reliability may optimize, re-interpret, or redesign theDCI payload to introduce new fields enabling the URLLC requiredfeatures, as well as optimizing the exiting fields to better suit thecharacteristics of URLLC traffic and obtain better link performance.This may result in a new DCI format that may be a new compact orsize-matched DCI format or a new size-matched DCI format such that: Newcompact or size-matched DCI format: Has DCI payload size lower than theDCI formats 0_0/1_0 for a given UL and/or DL BWP sizes; and Newsize-matched DCI format: Has DCI payload size that is matched to DCIformat 0_1 for UL scheduling and matched to DCI format 1_1 for DLscheduling—in this case, these two new DL and UL DCI formats may not besize-matched between DL and UL formats.

Other embodiments may be directed to mechanisms for optimizing DCIformats 0_0/0_1 and 1_0/1_1, as well as for configuring and using a newcompact or size-matched DCI format for DL and UL scheduling, consideringURLLC use cases.

The new compact or size-matched DCI formats are referred to as DCIformats 0_2 and 1_2 for UL and DL scheduling in a cell respectively.

In some embodiments, the new DCI formats 0_2/1_2 are only introduced toenable new features and their corresponding signaling. If no new DCIfield is added, the existing fallback/non-fallback formats are used andtheir corresponding fields may be further optimized and re-interpreted.In another embodiment, new fields may be added to DCI format 0_1 or 1_1or both, the presence of which fields and their bit-widths may depend onhigher layer configuration of related features.

Embodiments that May be Directed to Configuration and Monitoring of DCIFormats 0_2/1_2.

In embodiments, the new DCI format is defined as an optional UEcapability. In embodiments, for a UE supporting monitoring of the newcompact or size-matched DCI formats, a UE may be configured usingUE-specific higher layer signaling with possible monitoring of DCIformats 0_2 and 1_2 first, before it may be configured to monitor forthese new compact or size-matched DCI formats as part of search spaceset configuration. Note that the DL and UL DCI formats may be assumed assize-matched when in a configured search space set.

In embodiments, for a UE supporting monitoring of the new compact orsize-matched DCI formats, the UE may be directly configured to monitorfor the new compact or size-matched DCI format as part of the searchspace set configuration via UE-specific higher layer signaling, withouta need to be first configured with separate UE-specific signaling.

Specifically, different approaches could be considered depending onwhether the new compact or size-matched DCI format may be configured formonitoring only in a UE-specific search space (USS) or a common searchspace (CSS).

In an example, the compact or size-matched DCI formats may only beconfigured for monitoring in a PDCCH UE-specific search space (USS).

In another example, the compact or size-matched DCI formats may beconfigured for monitoring in a PDCCH UE-specific search space or in acommon search space (CSS). Further, in an example, for configuration ofmonitoring in a common search space, the configuration of the searchspace set may be provided to the UE via UE-specific signaling, and thus,the new compact or size-matched DCI format in this example may beconfigured for monitoring in Type 3 PDCCH CSS as defined in TS 38.23 v.15.1, in addition to PDCCH USS.

In another example, the UE may be configured with monitoring of eitherof DCI format 0_2 or format 1_2 for UL or DL scheduling respectively ina configured search space set, and for scheduling of the other linkdirection (for example, DL or UL respectively), the corresponding“fallback DCI format”, for example, DCI format 1_0 and 0_0 for DL and ULscheduling respectively, is assumed, and these two DCI formats aresize-matched in a configured search space set. In this case, the headerfield for format identification within one of DCI formats may indicatebetween DCI formats 0_0/0_1 and 1_2, or formats 0_2 and 1_0/1_1.

In an embodiment, the compact or size-matched DCI formats 0_2/1_2 aretransmitted with cyclical redundancy check (CRC) scrambled with eitherC-radio network temporary identifier (RNTI) or CS-RNTI or otherconfigurable RNTI.

Embodiments that May be Directed to Monitoring of Compact orSize-Matched DCI Format in Common Search Spaces

If the new compact or size-matched DCI format is introduced andconfigured for monitoring in a PDCCH CSS, according to embodiments, anew higher layer parameter may be used as part of the search space setconfiguration, that may be conveyed via UE-specific RRC signaling, toindicate whether to monitor for DCI formats 0_0/1_0 or DCI formats0_2/1_2 with CRC scrambled with C-RNTI or CS-RNTI or other configurableRNTI. This approach can avoid increase in UE blind decoding (BD) effortsor increase in the number of different DCI format sizes scrambled withC-RNTI or CS-RNTI, when configured for monitoring for compact orsize-matched DCI formats. This is achieved by effectively using the DCIformats 0_2/1_2 for supporting fallback operations, instead of DCIformats 0_0/1_0.

Additionally, if DCI formats 2_2 and 2_3 are configured to be monitoredin the same search space set, their payload sizes may be matched, usingzero padding as necessary, to the size corresponding to DCI format sizes0_0/1_0 or the size corresponding to DCI format sizes 0_2/1_2respectively.

Embodiments it May be Directed to Monitoring of Compact or Size-MatchedDCI Format in UE-Specific Search Spaces

If the compact or size-matched DCI format is introduced and configuredfor monitoring in a PDCCH USS, in embodiments, the higher layer fieldUSS-DCI-format may be extended to 2-bit field to indicate choice betweenDCI formats: 0_0/1_0, 0_1 & 1_1 (note: DCI formats 0_1 and 1_1 may nothave the same size), or 0_2/1_2 (compact or size-matched DCI format) tobe monitored.

This approach can help avoid increase in BD, which may be blinddecoding, efforts and number of different DCI format sizes when CRC isscrambled with C-RNTI or CS-RNTI.

In embodiments, the last code-point of the extended field USS-DCI-formatmay be used to indicate monitoring of 0_2/1_2 and 0_1 and 1_1 (the“non-fallback formats” for DL and UL scheduling), as long as the DCIsize budget is not violated. Note that the current DCI size budget isdefined as no more than 3 DCI format sizes for PDCCH with CRC scrambledwith C-RNTI or CS-RNTI and one additional DCI format size for any othervalid DCI format/RNTI combination. In embodiments, the DCI size budgetis extended for UEs supporting DCI formats 0_2/1_2 to maximum of fourDCI format sizes for PDCCH with CRC scrambled with C-RNTI or CS-RNTI andone additional DCI format size for other format/RNTI combination.

For the above embodiments, in other examples, a separate higher layerconfigured parameter as part of the search space set configuration maybe used to indicate the choice of DCI formats to be monitored in theUSS, instead of extending the existing parameter USS-DCI-format.

In various embodiments, when the new format is introduced, the UE can beconfigured as part of the search space set configuration inPDCCH-Configuration, to monitor in the UE-SS between non-fallback DCIformats, and new DCI formats.

In various embodiments, it is possible that the new DCI formatintroduced, is size-matched to the existing non-fallback format to avoidintroducing a new DCI size, if both versions of non-fallback formats(for example, DCI formats 0_1/1_1 and 0_2/1_2) are configured to bemonitored in a PDCCH search space set. In an example, if the UE isexpected to monitor for both non-fallback DCI formats, and new DCIformat, identification between these two formats is defined byintroducing new RNTIs for URLLC or a new header bit field or extendingthe existing header bit-field that would apply to both sets of DCIformats 0_1/1_1 and 0_2/1_2.

In various embodiments, indication of the DCI format betweennon-fallback and new DCI formats to the UE is done by means of BWPindication field, configuring two BWPs (potentially of samecharacteristics) each associated with one of size-matched DCI formats.The UE monitors only one of the formats in each BWP. The RRCconfiguration then refers to the configured active BWP, meaning thateach of the higher layer configurations are specific to BWP. Once the UEis pointed to a particular BWP, the corresponding RRC configurationreveals the set of enabled features/capabilities for that BWP, and therest of DCI fields are interpreted accordingly.

In the above, the use of CS-RNTI may indicate that, when in the samesearch space set, for DCI transmitted using PDCCH with CRC scrambledwith CS-RNTI (for Configured Grant-based (CG) PUSCH or Semi-PersistentlyScheduled (SPS) PDSCH), the DCI format may correspond to the DCI formatconfigured for monitoring by the higher layer parameter, viz., eitherof: compact or size-matched DCI formats (0_2/1_2), the fallback DCIformats (0_0/1_0), or the non-fallback DCI formats (0_1/1_1), or forboth compact and non-fallback formats.

If simultaneous monitoring of DCI formats 0_1/1_1 and 0_2/1_2 areconfigured in a search space set, in another example, the DCI format tobe monitored with CRC scrambled with CS-RNTI may be additionallyindicated between the formats 0_1/1_1 and 0_2/1_2 via a separate higherlayer parameter. Alternatively, if simultaneous monitoring of DCIformats 0_1/1_1 and 0_2/1_2 are configured in a search space set, theDCI format to be monitored with CRC scrambled with CS-RNTI is the DCIformat 0_2/1_2 by default.

In embodiments, the minimum requirements on BD efforts per slot and thenumber of CCEs for channel estimation during a slot duration are thesame, irrespective of support and configuration of monitoring of compactor size-matched DCI format. Note that although some of the followingembodiments are described with respect to the requirements on thenumbers of BDs and numbers of non-overlapping CCEs for channelestimation, the embodiments may apply to either or both of these tworequirements.

In other embodiments, a UE capability corresponding to increased numbersof BDs and CCEs for channel estimation per slot may be defined for PDCCHmonitoring case 2 (e.g., when PDCCH monitoring is configured withmonitoring periodicity less than slot duration).

Further, in an extension of such embodiments, the numbers of BDs andCCEs are defined per slot or per half-slot, with the total numbers ofBDs and CCEs per slot being larger than the numbers cited above for Case2, however, the number of BDs and CCEs over any span of ‘p’ consecutiveOFDM symbols may not increase the corresponding values defined for Case1-1 (that are equal to the numbers for Case 2 as currently specified)for the respective subcarrier spacing (SCS) value, with p equal to onefixed value from the set {3, . . . , 7}. In an example, p=3.

Further, if a UE is configured to monitor both DCI formats 0_1/1_1 and0_2/1_2 in a PDCCH USS, PDCCH candidate dropping rules may be defined inan example such that the PDCCH candidates corresponding to DCI formats0_1/1_1 may be selected for dropping over candidates corresponding toDCI formats 0_2/1_2 in case either or both of the minimum requirementson number of BD attempts or number of CCEs in a slot is/are exceeded.

Embodiments Directed to Adaptations to Certain Bit-Fields for New DCIFormats 0_2/1_2 or Existing Fallback/Non-Fallback Formats

Various embodiments may be directed to realize reduced or entire removalof bit-field sizes in fallback/non-fallback formats.

Embodiments herein may be directed to specific fields, such as frequencyand time domain resource allocation (RA), and Modulation and CodingScheme (MCS) indication.

Embodiments Directed to Frequency-Domain RA:

The frequency domain RA following Type 1 RA may be adapted to scheduleusing a granularity of K>1 PRBs. The corresponding number of bits in thefrequency domain RA field in the DCI format is given byceil(log_2(ceil(N_(RB) ^(XL,BWP)/K)*(ceil(N_(RB) ^(XL,BWP)/K)+1)/2)),with XL=DL or UL.

In such a case, in embodiments, the value of K may be set separately forDL and UL as a new higher layer parameter via UE-specific radio resourcecontrol (RRC) signaling on a per-bandwidth part (BWP) basis. Inalternative embodiments, the value of K could be same as the ResourceBlock Group (RBG) size corresponding to Configuration #2 as specifiedfor a given BWP size (see table below). In alternative embodiments, thevalue of K could be configured to use RBG sizes for the BWP from eitherRBG configuration #1 or #2.

TABLE 5.1.2.2.1-1 Nominal RBG size P Bandwidth Part Size Configuration 1Configuration 2  1-36 2 4 37-72 4 8  73-144 8 16 145-275 16 16

Further, in an example, the indexing of the K-PRB contiguous frequencyresources within a BWP can be such that the lowest PRB index of the BWPmarks the first K-PRB set, with the last PRB-set possibly having fewerthan K PRBs. Such an allocation approach may requireceil(log_2(ceil(N_(RB) ^(XL,BWP)/K)*(ceil(N_(RB) ^(XL,BWP)/K)+1)/2))bits as mentioned above.

In another example, the indexing of the K-PRB contiguous frequencyresources within a BWP can be similar to the approach used for indexingof RBGs within a BWP. That is, the total number of K-PRB sets(N_(K-PRB)) for a DL or UL carrier BWP i of size N_(BWP,i) ^(size) PRBsis given by N_(K-PRB) ceil ((N_(BWP,i) ^(size)+(N_(BWP,i) ^(start) modK))/K), where

-   -   the size of the first K-PRB set is given by (K−_(BWP,i) ^(start)        mod K),    -   the size of last RBG is given by (N_(BWP,i) ^(start)+N_(BWP,i)        ^(size)) mod K, if (N_(BWP,i) ^(start)+N_(BWP,i) ^(size)) mod        K>0 and equals K otherwise,    -   the size of all other K-PRB sets is K.

The latter approach may require more up to one more bit compared to thefirst approach, but can offer better alignment with other RA types(especially RA type 0) if used in the same BWP or in other overlappedBWPs.

Embodiments Directed to Time-Domain RA:

In embodiments, only PDSCH and PUSCH mapping type B may be used fortime-domain scheduling when using DCI formats 1_2 and 02 respectively.In embodiments, only mapping type B may be used for PUSCH schedulingusing DCI format 02, but both mapping types A and B are supported forPDSCH when scheduled using DCI format 1_2. The latter offers additionflexibility for PDSCH scheduling since PDSCH with mapping type B onlysupports PDSCH durations of 2, 4, and 7 symbols.

In embodiments, for scheduling of PDSCH, the maximum duration of thescheduled PDSCH is indicated at least in part based on the maximumAggregation Level (AL) or maximum Repetition Level (RL) defined for thesearch space set where the scheduling PDCCH is detected, or,alternatively, based on the AL or RL used for PDCCH candidate used totransmit the scheduling DCI.

In embodiments, the slot offset value between PDCCH and scheduled PDSCH,K0, may be indicated from a set of values that is restricted to a lowermaximum value than when scheduling using DCI formats 1_0 or 1_1(specified max of 32). For instance, the possible set of K0 values canbe specified as fixed to {0}, or {0, 1} or {0, 1, 2} or {0, 1, 2, 3},etc., when scheduled using DCI format 1_2. In an example, the set ofpossible values that a UE may be configured with by higher layers for K0is not restricted, but it may be specified that the UE does not expectto receive a time-domain resource allocation indicating K0 value beyondthe set of values as in the examples above.

Similarly, in embodiments, the slot offset value between PDCCH andscheduled PUSCH, K2, may be indicated from a set of values that isrestricted to a lower maximum value than when scheduling using DCIformats 0_0 or 0_1 (specified max of 32). For instance, the possible setof K2 values can be specified as {0, 1, 2, 3, 4} or {0, 1, 2}, etc.,when scheduled using DCI format 0_2. In an example, the set of possiblevalues that a UE may be configured with by higher layers for K2 is notrestricted, but it is specified that the UE does not expect to receive atime-domain resource allocation indicating K2 value beyond the set ofvalues as in the examples above.

The above restrictions on the maximum values of K0 and K2 are motivatedby the aim to reduce possible signaling combinations and the expectedlatency-sensitive use cases for DCI formats 02/1_2 precluding use oflarge values of K0 or K2.

In embodiments, the set of possible K0 or K2 values are defined as afunction of the subcarrier spacing (SCS).

In embodiments, only certain combinations of the values of K0/K2, Startand Length Indicator Value (SLIV), and the PDSCH/PUSCH mapping type maybe configured to the UE to construct the different rows of thetime-domain resource allocation table that would be used by thetime-domain resource allocation field in the DCI formats 0_2/1_2respectively.

In legacy specifications, a UE may be configured with slot aggregationfactor semi-statically via higher layers for PDSCH or PUSCH. In suchcases, the scheduled PDSCH/PUSCH are expected to be repeated accordingto the indicated slot aggregation factor.

However, this may not provide sufficiently flexible link adaptationcapability for URLLC use cases. To overcome this restriction, inembodiments, based on UE-specific configuration of dynamically indicatednumbers of repetitions of the PDSCH/PUSCH, a field in the DCI may beused to dynamically indicate the number of repetitions. The set ofcandidate values may be pre-defined or configured via UE-specificsignaling. Such configurations can be separate for DL and UL.

The new bit-field could be configured for new compact or size-matchedDCI formats 0_2/1_2 (if introduced) and/or to non-fallback DCI formats0_1/1_1. If introduced to DCI formats 0_2/1_2, the new field may bepresent only when the DCI format is monitored in the PDCCH USS.

In embodiments, for scheduling of PDSCH, instead of explicit indicationof the number of repetitions used for the scheduled PDSCH, theinformation is indicated at least in part based on the maximumAggregation Level (AL) or maximum Repetition Level (RL) defined for thesearch space set where the scheduling PDCCH is detected, or,alternatively, based on the AL or RL used for PDCCH candidate used totransmit the scheduling DCI.

Embodiments that May be Directed to MCS Field:

In embodiments, the MCS field for scheduling PDSCH or PUSCH in a compactor size-matched DCI format 1_2 or 0_2 respectively and/or innon-fallback DCI formats 1_1 and 0_1 respectively can be reduced from 5bit to 4 or 3 bit. The mapping of 32 entries to 16 or 8 entriesrespectively for 4 or 3 bit tables may be either predefined or besemi-statically configurable via UE-specific (re)configuration RRCmessage.

The mapping of 5 bit tables to smaller tables can be realized usingcombinatorial index approach similar to the one used for EPDCCH orSPDCCH PRB-pair resource set configuration. That is, a combinatorialindex r corresponding to the MCS index from 5-bita table {k_(i)}_(i=0)^(M), (1≤k_(i)≤M₀,k_(i)<k_(i+1)) and given by equation

${\sum\limits_{i = 0}^{M - 1}\;\left\langle \begin{matrix}{M_{0} - k_{i}} \\{M - k_{i}}\end{matrix} \right\rangle},$where M₀ is the number of MCS entries in a 5-bit table defined for 64QAMor 256QAM for PDSCH or PUSCH, M₀ is the number of MCS entries in acompressed MCS table derived as M=2^(L), where L is the number of bitsconfigured for the compressed MCS index indication, and M is configuredby higher layers and

$\left\langle \begin{matrix}x \\y\end{matrix} \right\rangle = \left\{ \begin{matrix}\begin{pmatrix}x \\y\end{pmatrix} & {x \geq y} \\0 & {x < y}\end{matrix} \right.$is the extended binomial coefficient, resulting in unique label

$r \in {\left\{ {0,\ldots\mspace{14mu},{\begin{pmatrix}M_{0} \\M\end{pmatrix} - 1}} \right\}.}$

Addition of certain bit-fields to new DCI formats 0_2/1_2 or DCI formats0_1/1_1 when configured.

New DCI fields can be added to the new or existing DCI formats, in orderto enable different URLLC-related functionalities.

In an embodiment, DL Pre-emption Indication (PI) is included in DCIformats 1_1 or DCI format 1_2, to indicate whether the current PDSCHassignment may be pre-empted or not.

FIG. 3 illustrates operation flows/algorithmic structures for a userequipment (UE) to monitor physical downlink control channel (PDCCH) toobtain the downlink control information in accordance with someembodiments. In particular, FIG. 3 illustrates an operationflow/algorithmic structure 300 that may be implemented by a device, orcomponents thereof, as described herein with respect to any one of FIGS.5-13.

The operation flow/algorithmic structure 300 may include, at 301,transmitting, to a base station, an indication of a capability of the UEto support a first downlink control information (DCI) format forPhysical Downlink Shared Channel (PDSCH) reception in a downlink (DL)bandwidth part (BWP) and a second DCI format for scheduling uplink (UL)grants for physical uplink shared channel (PUSCH) transmission in a ULbandwidth part (BWP), where the first DCI format is different from DCIformats 1_0 or 1_1, and the second DCI format is different from DCIformats 0_0 or 0_1. In some embodiments, the transmitting to the basestation an indication of a capability of the UE may be performed bynetwork controller circuitry in, for example, radio front end module 715or 815, or network controller circuitry 735, or antenna 920.

The operation flow/algorithmic structure 300 may further include, at303, determining search spaces for monitoring physical downlink controlchannel (PDCCH) candidates to obtain DCI formats indicated by the basestation. In some embodiments, the determining the search spaces may beperformed by processing circuitry in, for example, application circuitry705 or 805, or baseband circuitry 710 or 810.

The operation flow/algorithmic structure 300 may further include, at305, monitoring the search spaces for the PDCCH candidates. In someembodiments, the monitoring the search spaces for the PDCCH candidatesmay be performed by processing circuitry in, for example, applicationcircuitry 705 or 805, or baseband circuitry 710 or 810.

The operation flow/algorithmic structure 300 may further include, at307, detecting the indicated DCI formats, wherein the indicated DCIformats are selected from the first DCI format, the second DCI format,the DCI format 1_0, the DCI format 1_1, the DCI format 0_0, or the DCIformat 0_1. In some embodiments, the detecting the indicated DCI formatsmay be performed by processing circuitry in, for example, applicationcircuitry 705 or 805, or baseband circuitry 710 or 810.

FIG. 4 illustrates operation flows/algorithmic structures for a basestation to transmit downlink control information by physical downlinkcontrol channel (PDCCH) in accordance with some embodiments. Inparticular, FIG. 4 illustrates an operation flow/algorithmic structure400 that may be implemented by a device, or components thereof, asdescribed herein with respect to any one of FIGS. 5-13.

The operation flow/algorithmic structure 400 may include, at 401,receiving or causing to receive, an indication of a capability of a userequipment (UE) to support a first downlink control information (DCI)format for Physical Downlink Shared Channel (PDSCH) reception in adownlink (DL) bandwidth part (BWP) and a second DCI format forscheduling uplink (UL) grants for physical uplink shared channel (PUSCH)transmission in a UL bandwidth part (BWP), where the first DCI format isdifferent from DCI formats 1_0 or 1_1, and the second DCI format aredifferent from DCI formats 0_0 or 0_1. In some embodiments, thereceiving or causing to receive, an indication of a capability of the UEmay be performed by network controller circuitry in, for example, radiofront end module 715 or 815, or network controller circuitry 735, orantenna 920.

The operation flow/algorithmic structure 400 may further include, at403, determining search spaces for the UE to monitor physical downlinkcontrol channel (PDCCH) candidates to obtain DCI formats indicated bythe base station. In some embodiments, the determining the search spacesmay be performed by processing circuitry in, for example, applicationcircuitry 705 or 805, or baseband circuitry 710 or 810.

The operation flow/algorithmic structure 400 may further include, at405, selecting a DCI formats from the first DCI format, the second DCIformat, the DCI format 1_0, the DCI format 1_1, the DCI format 0_0, orthe DCI format 0_1, the DCI formats to be indicated to the UE. In someembodiments, the selecting a DCI formats may be performed by processingcircuitry in, for example, application circuitry 705 or 805, or basebandcircuitry 710 or 810.

The operation flow/algorithmic structure 400 may further include, at407, transmitting, to the UE, the selected DCI formats. In someembodiments, the detecting the indicated DCI formats may be performed bynetwork controller circuitry in, for example, radio front end module 715or 815, or network controller circuitry 735, or antenna 920.

FIG. 5 illustrates an architecture of a system 500 of a network inaccordance with some embodiments. The system 500 is shown to include auser equipment (UE) 501 and a UE 502. As used herein, the term “userequipment” or “UE” may refer to a device with radio communicationcapabilities and may describe a remote user of network resources in acommunications network. The term “user equipment” or “UE” may beconsidered synonymous to, and may be referred to as client, mobile,mobile device, mobile terminal, user terminal, mobile unit, mobilestation, mobile user, subscriber, user, remote station, access agent,user agent, receiver, radio equipment, reconfigurable radio equipment,reconfigurable mobile device, etc. Furthermore, the term “userequipment” or “UE” may include any type of wireless/wired device or anycomputing device including a wireless communications interface. In thisexample, UEs 501 and 502 are illustrated as smartphones (e.g., handheldtouchscreen mobile computing devices connectable to one or more cellularnetworks), but may also comprise any mobile or non-mobile computingdevice, such as consumer electronics devices, cellular phones,smartphones, feature phones, tablet computers, wearable computerdevices, personal digital assistants (PDAs), pagers, wireless handsets,desktop computers, laptop computers, in-vehicle infotainment (IVI),in-car entertainment (ICE) devices, an Instrument Cluster (IC), head-updisplay (HUD) devices, onboard diagnostic (OBD) devices, dashtop mobileequipment (DME), mobile data terminals (MDTs), Electronic EngineManagement System (EEMS), electronic/engine control units (ECUs),electronic/engine control modules (ECMs), embedded systems,microcontrollers, control modules, engine management systems (EMS),networked or “smart” appliances, machine-type communications (MTC)devices, machine-to-machine (M2M), Internet of Things (IoT) devices,and/or the like.

In some embodiments, any of the UEs 501 and 502 can comprise an Internetof Things (IoT) UE, which can comprise a network access layer designedfor low-power IoT applications utilizing short-lived UE connections. AnIoT UE can utilize technologies such as machine-to-machine (M2M) ormachine-type communications (MTC) for exchanging data with an MTC serveror device via a public land mobile network (PLMN), Proximity-BasedService (ProSe) or device-to-device (D2D) communication, sensornetworks, or IoT networks. The M2M or MTC exchange of data may be amachine-initiated exchange of data. An IoT network describesinterconnecting IoT UEs, which may include uniquely identifiableembedded computing devices (within the Internet infrastructure), withshort-lived connections. The IoT UEs may execute background applications(e.g., keep-alive messages, status updates, etc.) to facilitate theconnections of the IoT network.

The UEs 501 and 502 may be configured to connect, e.g., communicativelycouple, with a radio access network (RAN) 510—the RAN 510 may be, forexample, an Evolved Universal Mobile Telecommunications System (UMTS)Terrestrial Radio Access Network (E-UTRAN), a NextGen RAN (NG RAN), orsome other type of RAN. The UEs 501 and 502 utilize connections (orchannels) 503 and 504, respectively, each of which comprises a physicalcommunications interface or layer (discussed in further detail infra).As used herein, the term “channel” may refer to any transmission medium,either tangible or intangible, which is used to communicate data or adata stream. The term “channel” may be synonymous with and/or equivalentto “communications channel,” “data communications channel,”“transmission channel,” “data transmission channel,” “access channel,”“data access channel,” “link,” “data link,” “carrier,” “radiofrequencycarrier,” and/or any other like term denoting a pathway or mediumthrough which data is communicated. Additionally, the term “link” mayrefer to a connection between two devices through a Radio AccessTechnology (RAT) for the purpose of transmitting and receivinginformation. In this example, the connections 503 and 504 areillustrated as an air interface to enable communicative coupling, andcan be consistent with cellular communications protocols, such as aGlobal System for Mobile Communications (GSM) protocol, a code-divisionmultiple access (CDMA) network protocol, a Push-to-Talk (PTT) protocol,a PTT over Cellular (POC) protocol, a Universal MobileTelecommunications System (UMTS) protocol, a 3GPP Long Term Evolution(LTE) protocol, a fifth generation (5G) protocol, a New Radio (NR)protocol, and the like.

In this embodiment, the UEs 501 and 502 may further directly exchangecommunication data via a ProSe interface 505. The ProSe interface 505may alternatively be referred to as a sidelink interface comprising oneor more logical channels, including but not limited to a PhysicalSidelink Control Channel (PSCCH), a Physical Sidelink Shared Channel(PSSCH), a Physical Sidelink Discovery Channel (PSDCH), and a PhysicalSidelink Broadcast Channel (PSBCH). In various implementations, the SLinterface 505 may be used in vehicular applications and communicationstechnologies, which are often referred to as V2X systems. V2X is a modeof communication where UEs (for example, UEs 501, 502) communicate witheach other directly over the PC5/SL interface 505 and can take placewhen the UEs 501, 502 are served by RAN nodes 511, 512 or when one ormore UEs are outside a coverage area of the RAN 510. V2X may beclassified into four different types: vehicle-to-vehicle (V2V),vehicle-to-infrastructure (V2I), vehicle-to-network (V2N), andvehicle-to-pedestrian (V2P). These V2X applications can use“co-operative awareness” to provide more intelligent services forend-users. For example, vUEs 501, 502, RAN nodes 511, 512, applicationservers 530, and pedestrian UEs 501, 502 may collect knowledge of theirlocal environment (for example, information received from other vehiclesor sensor equipment in proximity) to process and share that knowledge inorder to provide more intelligent services, such as cooperativecollision warning, autonomous driving, and the like. In theseimplementations, the UEs 501, 502 may be implemented/employed as VehicleEmbedded Communications Systems (VECS) or vUEs.

The UE 502 is shown to be configured to access an access point (AP) 506(also referred to as also referred to as “WLAN node 506”, “WLAN 506”,“WLAN Termination 506” or “WT 506” or the like) via connection 507. Theconnection 507 can comprise a local wireless connection, such as aconnection consistent with any IEEE 802.11 protocol, wherein the AP 506would comprise a wireless fidelity (WiFi®) router. In this example, theAP 506 is shown to be connected to the Internet without connecting tothe core network of the wireless system (described in further detailbelow). In various embodiments, the UE 502, RAN 510, and AP 506 may beconfigured to utilize LTE-WLAN aggregation (LWA) operation and/or WLANLTE/WLAN Radio Level Integration with IPsec Tunnel (LWIP) operation. TheLWA operation may involve the UE 502 in RRC_CONNECTED being configuredby a RAN node 511, 512 to utilize radio resources of LTE and WLAN. LWIPoperation may involve the UE 502 using WLAN radio resources (e.g.,connection 507) via Internet Protocol Security (IPsec) protocoltunneling to authenticate and encrypt packets (e.g., internet protocol(IP) packets) sent over the connection 507. IPsec tunneling may includeencapsulating entirety of original IP packets and adding a new packetheader thereby protecting the original header of the IP packets.

The RAN 510 can include one or more access nodes that enable theconnections 503 and 504. As used herein, the terms “access node,”“access point,” or the like may describe equipment that provides theradio baseband functions for data and/or voice connectivity between anetwork and one or more users. These access nodes can be referred to asbase stations (BS), NodeBs, evolved NodeBs (eNBs), next GenerationNodeBs (gNB), RAN nodes, Road Side Units (RSUs), and so forth, and cancomprise ground stations (e.g., terrestrial access points) or satellitestations providing coverage within a geographic area (e.g., a cell). Theterm “Road Side Unit” or “RSU” may refer to any transportationinfrastructure entity implemented in or by an gNB/eNB/RAN node or astationary (or relatively stationary) UE, where an RSU implemented in orby a UE may be referred to as a “UE-type RSU”, an RSU implemented in orby an eNB may be referred to as an “eNB-type RSU.” The RAN 510 mayinclude one or more RAN nodes for providing macrocells, e.g., macro RANnode 511, and one or more RAN nodes for providing femtocells orpicocells (e.g., cells having smaller coverage areas, smaller usercapacity, or higher bandwidth compared to macrocells), e.g., low power(LP) RAN node 512.

Any of the RAN nodes 511 and 512 can terminate the air interfaceprotocol and can be the first point of contact for the UEs 501 and 502.In some embodiments, any of the RAN nodes 511 and 512 can fulfillvarious logical functions for the RAN 510 including, but not limited to,radio network controller (RNC) functions such as radio bearermanagement, uplink and downlink dynamic radio resource management anddata packet scheduling, and mobility management.

In accordance with some embodiments, the UEs 501 and 502 can beconfigured to communicate using Orthogonal Frequency-DivisionMultiplexing (OFDM) communication signals with each other or with any ofthe RAN nodes 511 and 512 over a multicarrier communication channel inaccordance various communication techniques, such as, but not limitedto, an Orthogonal Frequency-Division Multiple Access (OFDMA)communication technique (e.g., for downlink communications) or a SingleCarrier Frequency Division Multiple Access (SC-FDMA) communicationtechnique (e.g., for uplink and ProSe or sidelink communications),although the scope of the embodiments is not limited in this respect.The OFDM signals can comprise a plurality of orthogonal subcarriers.

In some embodiments, a downlink resource grid can be used for downlinktransmissions from any of the RAN nodes 511 and 512 to the UEs 501 and502, while uplink transmissions can utilize similar techniques. The gridcan be a time-frequency grid, called a resource grid or time-frequencyresource grid, which is the physical resource in the downlink in eachslot. Such a time-frequency plane representation is a common practicefor OFDM systems, which makes it intuitive for radio resourceallocation. Each column and each row of the resource grid corresponds toone OFDM symbol and one OFDM subcarrier, respectively. The duration ofthe resource grid in the time domain corresponds to one slot in a radioframe. The smallest time-frequency unit in a resource grid is denoted asa resource element. Each resource grid comprises a number of resourceblocks, which describe the mapping of certain physical channels toresource elements. Each resource block comprises a collection ofresource elements; in the frequency domain, this may represent thesmallest quantity of resources that currently can be allocated. Thereare several different physical downlink channels that are conveyed usingsuch resource blocks.

The physical downlink shared channel (PDSCH) may carry user data andhigher-layer signaling to the UEs 501 and 502. The physical downlinkcontrol channel (PDCCH) may carry information about the transport formatand resource allocations related to the PDSCH channel, among otherthings. It may also inform the UEs 501 and 502 about the transportformat, resource allocation, and H-ARQ (Hybrid Automatic Repeat Request)information related to the uplink shared channel. Typically, downlinkscheduling (assigning control and shared channel resource blocks to theUE 502 within a cell) may be performed at any of the RAN nodes 511 and512 based on channel quality information fed back from any of the UEs501 and 502. The downlink resource assignment information may be sent onthe PDCCH used for (e.g., assigned to) each of the UEs 501 and 502.

The PDCCH may use control channel elements (CCEs) to convey the controlinformation. Before being mapped to resource elements, the PDCCHcomplex-valued symbols may first be organized into quadruplets, whichmay then be permuted using a sub-block interleaver for rate matching.Each PDCCH may be transmitted using one or more of these CCEs, whereeach CCE may correspond to nine sets of four physical resource elementsknown as resource element groups (REGs). Four Quadrature Phase ShiftKeying (QPSK) symbols may be mapped to each REG. The PDCCH can betransmitted using one or more CCEs, depending on the size of thedownlink control information (DCI) and the channel condition. There canbe four or more different PDCCH formats defined in LTE with differentnumbers of CCEs (e.g., aggregation level, L=1, 2, 4, or 8).

Some embodiments may use concepts for resource allocation for controlchannel information that are an extension of the above-describedconcepts. For example, some embodiments may utilize an enhanced physicaldownlink control channel (EPDCCH) that uses PDSCH resources for controlinformation transmission. The EPDCCH may be transmitted using one ormore enhanced the control channel elements (ECCEs). Similar to above,each ECCE may correspond to nine sets of four physical resource elementsknown as an enhanced resource element groups (EREGs). An ECCE may haveother numbers of EREGs in some situations.

The RAN 510 is shown to be communicatively coupled to a core network(CN) 520—via an S1 interface 513. In embodiments, the CN 520 may be anevolved packet core (EPC) network, a NextGen Packet Core (NPC) network,or some other type of CN. In this embodiment the S1 interface 513 issplit into two parts: the S1-U interface 514, which carries traffic databetween the RAN nodes 511 and 512 and the serving gateway (S-GW) 522,and the S1-mobility management entity (MME) interface 515, which is asignaling interface between the RAN nodes 511 and 512 and MMEs 521.

In this embodiment, the CN 520 comprises the MMEs 521, the S-GW 522, thePacket Data Network (PDN) Gateway (P-GW) 523, and a home subscriberserver (HSS) 524. The MMEs 521 may be similar in function to the controlplane of legacy Serving General Packet Radio Service (GPRS) SupportNodes (SGSN). The MMEs 521 may manage mobility aspects in access such asgateway selection and tracking area list management. The HSS 524 maycomprise a database for network users, including subscription-relatedinformation to support the network entities' handling of communicationsessions. The CN 520 may comprise one or several HSSs 524, depending onthe number of mobile subscribers, on the capacity of the equipment, onthe organization of the network, etc. For example, the HSS 524 canprovide support for routing/roaming, authentication, authorization,naming/addressing resolution, location dependencies, etc.

The S-GW 522 may terminate the S1 interface 513 towards the RAN 510, androutes data packets between the RAN 510 and the CN 520. In addition, theS-GW 522 may be a local mobility anchor point for inter-RAN nodehandovers and also may provide an anchor for inter-3GPP mobility. Otherresponsibilities may include lawful intercept, charging, and some policyenforcement.

The P-GW 523 may terminate an SGi interface toward a PDN. The P-GW 523may route data packets between the EPC network 523 and external networkssuch as a network including the application server 530 (alternativelyreferred to as application function (AF)) via an Internet Protocol (IP)interface 525. Generally, the application server 530 may be an elementoffering applications that use IP bearer resources with the core network(e.g., UMTS Packet Services (PS) domain, LTE PS data services, etc.). Inthis embodiment, the P-GW 523 is shown to be communicatively coupled toan application server 530 via an IP communications interface 525. Theapplication server 530 can also be configured to support one or morecommunication services (e.g., Voice-over-Internet Protocol (VoIP)sessions, PTT sessions, group communication sessions, social networkingservices, etc.) for the UEs 501 and 502 via the CN 520.

The P-GW 523 may further be a node for policy enforcement and chargingdata collection. Policy and Charging Enforcement Function (PCRF) 526 isthe policy and charging control element of the CN 520. In a non-roamingscenario, there may be a single PCRF in the Home Public Land MobileNetwork (HPLMN) associated with a UE's Internet Protocol ConnectivityAccess Network (IP-CAN) session. In a roaming scenario with localbreakout of traffic, there may be two PCRFs associated with a UE'sIP-CAN session: a Home PCRF (H-PCRF) within a HPLMN and a Visited PCRF(V-PCRF) within a Visited Public Land Mobile Network (VPLMN). The PCRF526 may be communicatively coupled to the application server 530 via theP-GW 523. The application server 530 may signal the PCRF 526 to indicatea new service flow and select the appropriate Quality of Service (QoS)and charging parameters. The PCRF 526 may provision this rule into aPolicy and Charging Enforcement Function (PCEF) (not shown) with theappropriate traffic flow template (TFT) and QoS class of identifier(QCI), which commences the QoS and charging as specified by theapplication server 530.

FIG. 6 illustrates an architecture of a system 600 of a network inaccordance with some embodiments. The system 600 is shown to include aUE 601, which may be the same or similar to UEs 501 and 502 discussedpreviously; a RAN node 611, which may be the same or similar to RANnodes 511 and 512 discussed previously; a Data network (DN) 603, whichmay be, for example, operator services, Internet access or 3rd partyservices; and a 5G Core Network (5GC or CN) 620.

The CN 620 may include an Authentication Server Function (AUSF) 622; anAccess and Mobility Management Function (AMF) 621; a Session ManagementFunction (SMF) 624; a Network Exposure Function (NEF) 623; a PolicyControl function (PCF) 626; a Network Function (NF) Repository Function(NRF) 625; a Unified Data Management (UDM) 627; an Application Function(AF) 628; a User Plane Function (UPF) 602; and a Network Slice SelectionFunction (NSSF) 629.

The UPF 602 may act as an anchor point for intra-RAT and inter-RATmobility, an external PDU session point of interconnect to DN 603, and abranching point to support multi-homed PDU session. The UPF 602 may alsoperform packet routing and forwarding, packet inspection, enforce userplane part of policy rules, lawfully intercept packets (UP collection);traffic usage reporting, perform QoS handling for user plane (e.g.packet filtering, gating, UL/DL rate enforcement), perform UplinkTraffic verification (e.g., SDF to QoS flow mapping), transport levelpacket marking in the uplink and downlink, and downlink packet bufferingand downlink data notification triggering. UPF 602 may include an uplinkclassifier to support routing traffic flows to a data network. The DN603 may represent various network operator services, Internet access, orthird party services. NY 603 may include, or be similar to applicationserver 930 discussed previously. The UPF 602 may interact with the SMF624 via an N4 reference point between the SMF 624 and the UPF 602.

The AUSF 622 may store data for authentication of UE 601 and handleauthentication related functionality. The AUSF 622 may facilitate acommon authentication framework for various access types. The AUSF 622may communicate with the AMF 621 via an N12 reference point between theAMF 621 and the AUSF 622; and may communicate with the UDM 627 via anN13 reference point between the UDM 627 and the AUSF 622. Additionally,the AUSF 622 may exhibit an Nausf service-based interface.

The AMF 621 may be responsible for registration management (e.g., forregistering UE 601, etc.), connection management, reachabilitymanagement, mobility management, and lawful interception of AMF-relatedevents, and access authentication and authorization. The AMF 621 may bea termination point for the an N11 reference point between the AMF 621and the SMF 624. The AMF 621 may provide transport for SessionManagement (SM) messages between the UE 601 and the SMF 624, and act asa transparent proxy for routing SM messages. AMF 621 may also providetransport for short message service (SMS) messages between UE 601 and anSMS function (SMSF) (not shown by FIG. 6). AMF 621 may act as SecurityAnchor Function (SEA), which may include interaction with the AUSF 622and the UE 601, receipt of an intermediate key that was established as aresult of the UE 601 authentication process. Where USIM basedauthentication is used, the AMF 621 may retrieve the security materialfrom the AUSF 622. AMF 621 may also include a Security ContextManagement (SCM) function, which receives a key from the SEA that ituses to derive access-network specific keys. Furthermore, AMF 621 may bea termination point of RAN CP interface, which may include or be an N2reference point between the (R)AN 611 and the AMF 621; and the AMF 621may be a termination point of NAS (N1) signalling, and perform NASciphering and integrity protection.

AMF 621 may also support NAS signalling with a UE 601 over an N3interworking-function (IWF) interface. The N3IWF may be used to provideaccess to untrusted entities. N3IWF may be a termination point for theN2 interface between the (R)AN 611 and the AMF 621 for the controlplane, and may be a termination point for the N3 reference point betweenthe (R)AN 611 and the UPF 602 for the user plane. As such, the AMF 621may handle N2 signalling from the SMF 624 and the AMF 621 for PDUsessions and QoS, encapsulate/de-encapsulate packets for IPSec and N3tunnelling, mark N3 user-plane packets in the uplink, and enforce QoScorresponding to N3 packet marking taking into account QoS requirementsassociated to such marking received over N2. N3IWF may also relay uplinkand downlink control-plane NAS signalling between the UE 601 and AMF 621via an N1 reference point between the UE 601 and the AMF 621, and relayuplink and downlink user-plane packets between the UE 601 and UPF 602.The N3IWF also provides mechanisms for IPsec tunnel establishment withthe UE 601. The AMF 621 may exhibit an Namf service-based interface, andmay be a termination point for an N14 reference point between two AMFs621 and an N17 reference point between the AMF 621 and a 5G-EquipmentIdentity Register (5G-EIR) (not shown by FIG. 6).

The SMF 624 may be responsible for session management (e.g., sessionestablishment, modify and release, including tunnel maintain between UPFand AN node); UE IP address allocation & management (including optionalAuthorization); Selection and control of UP function; Configures trafficsteering at UPF to route traffic to proper destination; termination ofinterfaces towards Policy control functions; control part of policyenforcement and QoS; lawful intercept (for SM events and interface to LISystem); termination of SM parts of NAS messages; downlink DataNotification; initiator of AN specific SM information, sent via AMF overN2 to AN; determine SSC mode of a session. The SMF 624 may include thefollowing roaming functionality: handle local enforcement to apply QoSSLAs (VPLMN); charging data collection and charging interface (VPLMN);lawful intercept (in VPLMN for SM events and interface to LI System);support for interaction with external DN for transport of signalling forPDU session authorization/authentication by external DN. An N16reference point between two SMFs 624 may be included in the system 600,which may be between another SMF 624 in a visited network and the SMF624 in the home network in roaming scenarios. Additionally, the SMF 624may exhibit the Nsmf service-based interface.

The NEF 623 may provide means for securely exposing the services andcapabilities provided by 3GPP network functions for third party,internal exposure/re-exposure, Application Functions (e.g., AF 628),edge computing or fog computing systems, etc. In such embodiments, theNEF 623 may authenticate, authorize, and/or throttle the AFs. NEF 623may also translate information exchanged with the AF 628 and informationexchanged with internal network functions. For example, the NEF 623 maytranslate between an AF-Service-Identifier and an internal 5GCinformation. NEF 623 may also receive information from other networkfunctions (NFs) based on exposed capabilities of other networkfunctions. This information may be stored at the NEF 623 as structureddata, or at a data storage NF using a standardized interfaces. Thestored information can then be re-exposed by the NEF 623 to other NFsand AFs, and/or used for other purposes such as analytics. Additionally,the NEF 623 may exhibit an Nnef service-based interface.

The NRF 625 may support service discovery functions, receive NFDiscovery Requests from NF instances, and provide the information of thediscovered NF instances to the NF instances. NRF 625 also maintainsinformation of available NF instances and their supported services. Asused herein, the terms “instantiate”, “instantiation”, and the like mayrefer to the creation of an instance, and an “instance” may refer to aconcrete occurrence of an object, which may occur, for example, duringexecution of program code. Additionally, the NRF 625 may exhibit theNnrf service-based interface.

The PCF 626 may provide policy rules to control plane function(s) toenforce them, and may also support unified policy framework to governnetwork behaviour. The PCF 626 may also implement a front end (FE) toaccess subscription information relevant for policy decisions in a UDRof the UDM 627. The PCF 626 may communicate with the AMF 621 via an N15reference point between the PCF 626 and the AMF 621, which may include aPCF 626 in a visited network and the AMF 621 in case of roamingscenarios. The PCF 626 may communicate with the AF 628 via an N5reference point between the PCF 626 and the AF 628; and with the SMF 624via an N7 reference point between the PCF 626 and the SMF 624. Thesystem 600 and/or CN 620 may also include an N24 reference point betweenthe PCF 626 (in the home network) and a PCF 626 in a visited network.Additionally, the PCF 626 may exhibit an Npcf service-based interface.

The UDM 627 may handle subscription-related information to support thenetwork entities' handling of communication sessions, and may storesubscription data of UE 601. For example, subscription data may becommunicated between the UDM 627 and the AMF 621 via an N8 referencepoint between the UDM 627 and the AMF 621 (not shown by FIG. 6). The UDM627 may include two parts, an application FE and a User Data Repository(UDR) (the FE and UDR are not shown by FIG. 6). The UDR may storesubscription data and policy data for the UDM 627 and the PCF 626,and/or structured data for exposure and application data (includingPacket Flow Descriptions (PFDs) for application detection, applicationrequest information for multiple UEs 601) for the NEF 623. The Nudrservice-based interface may be exhibited by the UDR 621 to allow the UDM627, PCF 626, and NEF 623 to access a particular set of the stored data,as well as to read, update (e.g., add, modify), delete, and subscribe tonotification of relevant data changes in the UDR. The UDM may include aUDM FE, which is in charge of processing of credentials, locationmanagement, subscription management and so on. Several different frontends may serve the same user in different transactions. The UDM-FEaccesses subscription information stored in the UDR and performsauthentication credential processing; user identification handling;access authorization; registration/mobility management; and subscriptionmanagement. The UDR may interact with the SMF 624 via an N10 referencepoint between the UDM 627 and the SMF 624. UDM 627 may also support SMSmanagement, wherein an SMS-FE implements the similar application logicas discussed previously. Additionally, the UDM 627 may exhibit the Nudmservice-based interface.

The AF 628 may provide application influence on traffic routing, accessto the Network Capability Exposure (NCE), and interact with the policyframework for policy control. The NCE may be a mechanism that allows the5GC and AF 628 to provide information to each other via NEF 623, whichmay be used for edge computing implementations. In such implementations,the network operator and third party services may be hosted close to theUE 601 access point of attachment to achieve an efficient servicedelivery through the reduced end-to-end latency and load on thetransport network. For edge computing implementations, the 5GC mayselect a UPF 602 close to the UE 601 and execute traffic steering fromthe UPF 602 to DN 603 via the N6 interface. This may be based on the UEsubscription data, UE location, and information provided by the AF 628.In this way, the AF 628 may influence UPF (re)selection and trafficrouting. Based on operator deployment, when AF 628 is considered to be atrusted entity, the network operator may permit AF 628 to interactdirectly with relevant NFs. Additionally, the AF 628 may exhibit an Nafservice-based interface.

The NSSF 629 may select a set of network slice instances serving the UE601. The NSSF 629 may also determine allowed Network Slice SelectionAssistance Information (NSSAI) and the mapping to the SubscribedSingle-NSSAIs (S-NSSAIs), if needed. The NSSF 629 may also determine theAMF set to be used to serve the UE 601, or a list of candidate AMF(s)621 based on a suitable configuration and possibly by querying the NRF625. The selection of a set of network slice instances for the UE 601may be triggered by the AMF 621 with which the UE 601 is registered byinteracting with the NSSF 629, which may lead to a change of AMF 621.The NSSF 629 may interact with the AMF 621 via an N22 reference pointbetween AMF 621 and NSSF 629; and may communicate with another NSSF 629in a visited network via an N31 reference point (not shown by FIG. 6).Additionally, the NSSF 629 may exhibit an Nnssf service-based interface.

As discussed previously, the CN 620 may include an SMSF, which may beresponsible for SMS subscription checking and verification, and relayingSM messages to/from the UE 601 to/from other entities, such as anSMS-GMSC/IWMSC/SMS-router. The SMS may also interact with AMF 621 andUDM 627 for notification procedure that the UE 601 is available for SMStransfer (e.g., set a UE not reachable flag, and notifying UDM 627 whenUE 601 is available for SMS).

The CN 620 may also include other elements that are not shown by FIG. 6,such as a Data Storage system/architecture, a 5G-Equipment IdentityRegister (5G-EIR), a Security Edge Protection Proxy (SEPP), and thelike. The Data Storage system may include a Structured Data Storagenetwork function (SDSF), an Unstructured Data Storage network function(UDSF), and/or the like. Any NF may store and retrieve unstructured datainto/from the UDSF (e.g., UE contexts), via N18 reference point betweenany NF and the UDSF (not shown by FIG. 6). Individual NFs may share aUDSF for storing their respective unstructured data or individual NFsmay each have their own UDSF located at or near the individual NFs.Additionally, the UDSF may exhibit an Nudsf service-based interface (notshown by FIG. 6). The 5G-EIR may be an NF that checks the status ofPermanent Equipment Identifiers (PEI) for determining whether particularequipment/entities are blacklisted from the network; and the SEPP may bea non-transparent proxy that performs topology hiding, messagefiltering, and policing on inter-PLMN control plane interfaces.

Additionally, there may be many more reference points and/orservice-based interfaces between the NF services in the NFs; however,these interfaces and reference points have been omitted from FIG. 6 forclarity. In one example, the CN 620 may include an Nx interface, whichis an inter-CN interface between the MME (e.g., MME 521) and the AMF 621in order to enable interworking between CN 620 and CN 520. Other exampleinterfaces/reference points may include an N5g-eir service-basedinterface exhibited by a 5G-EIR, an N27 reference point between NRF inthe visited network and the NRF in the home network; and an N31reference point between the NSSF in the visited network and the NSSF inthe home network.

In yet another example, system 600 may include multiple RAN nodes 611wherein an Xn interface is defined between two or more RAN nodes 611(e.g., gNBs and the like) that connecting to 5GC 620, between a RAN node611 (e.g., gNB) connecting to 5GC 620 and an eNB (e.g., a RAN node 511of FIG. 5), and/or between two eNBs connecting to 5GC 620. In someimplementations, the Xn interface may include an Xn user plane (Xn-U)interface and an Xn control plane (Xn-C) interface. The Xn-U may providenon-guaranteed delivery of user plane PDUs and support/provide dataforwarding and flow control functionality. The Xn-C may providemanagement and error handling functionality, functionality to manage theXn-C interface; mobility support for UE 601 in a connected mode (e.g.,CM-CONNECTED) including functionality to manage the UE mobility forconnected mode between one or more RAN nodes 611. The mobility supportmay include context transfer from an old (source) serving RAN node 611to new (target) serving RAN node 611; and control of user plane tunnelsbetween old (source) serving RAN node 611 to new (target) serving RANnode 611. A protocol stack of the Xn-U may include a transport networklayer built on Internet Protocol (IP) transport layer, and a GTP-U layeron top of a UDP and/or IP layer(s) to carry user plane PDUs. The Xn-Cprotocol stack may include an application layer signaling protocol(referred to as Xn Application Protocol (Xn-AP)) and a transport networklayer that is built on an SCTP layer. The SCTP layer may be on top of anIP layer. The SCTP layer provides the guaranteed delivery of applicationlayer messages. In the transport IP layer point-to-point transmission isused to deliver the signaling PDUs. In other implementations, the Xn-Uprotocol stack and/or the Xn-C protocol stack may be same or similar tothe user plane and/or control plane protocol stack(s) shown anddescribed herein.

FIG. 7 illustrates an example of infrastructure equipment 700 inaccordance with various embodiments. The infrastructure equipment 700(or “system 700”) may be implemented as a base station, radio head, RANnode, etc., such as the RAN nodes 511 and 512, and/or AP 506 shown anddescribed previously. In other examples, the system 700 could beimplemented in or by a UE, application server(s) 530, and/or any otherelement/device discussed herein. The system 700 may include one or moreof application circuitry 705, baseband circuitry 710, one or more radiofront end modules 715, memory 720, power management integrated circuitry(PMIC) 725, power tee circuitry 730, network controller 735, networkinterface connector 740, satellite positioning circuitry 745, and userinterface 750. In some embodiments, the device XT00 may includeadditional elements such as, for example, memory/storage, display,camera, sensor, or input/output (I/O) interface. In other embodiments,the components described below may be included in more than one device(e.g., said circuitries may be separately included in more than onedevice for Cloud-RAN (C-RAN) implementations).

As used herein, the term “circuitry” may refer to, is part of, orincludes hardware components such as an electronic circuit, a logiccircuit, a processor (shared, dedicated, or group) and/or memory(shared, dedicated, or group), an Application Specific IntegratedCircuit (ASIC), a field-programmable device (FPD), (for example, afield-programmable gate array (FPGA), a programmable logic device (PLD),a complex PLD (CPLD), a high-capacity PLD (HCPLD), a structured ASIC, ora programmable System on Chip (SoC)), digital signal processors (DSPs),etc., that are configured to provide the described functionality. Insome embodiments, the circuitry may execute one or more software orfirmware programs to provide at least some of the describedfunctionality. In addition, the term “circuitry” may also refer to acombination of one or more hardware elements (or a combination ofcircuits used in an electrical or electronic system) with the programcode used to carry out the functionality of that program code. In theseembodiments, the combination of hardware elements and program code maybe referred to as a particular type of circuitry.

The terms “application circuitry” and/or “baseband circuitry” may beconsidered synonymous to, and may be referred to as “processorcircuitry.” As used herein, the term “processor circuitry” may refer to,is part of, or includes circuitry capable of sequentially andautomatically carrying out a sequence of arithmetic or logicaloperations; recording, storing, and/or transferring digital data. Theterm “processor circuitry” may refer to one or more applicationprocessors, one or more baseband processors, a physical centralprocessing unit (CPU), a single-core processor, a dual-core processor, atriple-core processor, a quad-core processor, and/or any other devicecapable of executing or otherwise operating computer-executableinstructions, such as program code, software modules, and/or functionalprocesses.

Furthermore, the various components of the core network 520 (or CN 620discussed infra) may be referred to as “network elements.” The term“network element” may describe a physical or virtualized equipment usedto provide wired or wireless communication network services. The term“network element” may be considered synonymous to and/or referred to asa networked computer, networking hardware, network equipment, networknode, router, switch, hub, bridge, radio network controller, radioaccess network device, gateway, server, virtualized network function(VNF), network functions virtualization infrastructure (NFVI), and/orthe like.

Application circuitry 705 may include one or more central processingunit (CPU) cores and one or more of cache memory, low drop-out voltageregulators (LDOs), interrupt controllers, serial interfaces such as SPI,I2C or universal programmable serial interface module, real time clock(RTC), timer-counters including interval and watchdog timers, generalpurpose input/output (I/O or IO), memory card controllers such as SecureDigital (SD/)MultiMediaCard (MMC) or similar, Universal Serial Bus (USB)interfaces, Mobile Industry Processor Interface (MIPI) interfaces andJoint Test Access Group (JTAG) test access ports. As examples, theapplication circuitry 705 may include one or more Intel Pentium®, Core®,or Xeon® processor(s); Advanced Micro Devices (AMD) Ryzen® processor(s),Accelerated Processing Units (APUs), or Epyc® processors; and/or thelike. In some embodiments, the system 700 may not utilize applicationcircuitry 705, and instead may include a special-purposeprocessor/controller to process IP data received from an EPC or 5GC, forexample.

Additionally or alternatively, application circuitry 705 may includecircuitry such as, but not limited to, one or more a field-programmabledevices (FPDs) such as field-programmable gate arrays (FPGAs) and thelike; programmable logic devices (PLDs) such as complex PLDs (CPLDs),high-capacity PLDs (HCPLDs), and the like; ASICs such as structuredASICs and the like; programmable SoCs (PSoCs); and the like. In suchembodiments, the circuitry of application circuitry 705 may compriselogic blocks or logic fabric including and other interconnectedresources that may be programmed to perform various functions, such asthe procedures, methods, functions, etc. of the various embodimentsdiscussed herein. In such embodiments, the circuitry of applicationcircuitry 705 may include memory cells (e.g., erasable programmableread-only memory (EPROM), electrically erasable programmable read-onlymemory (EEPROM), flash memory, static memory (e.g., static random accessmemory (SRAM), anti-fuses, etc.) used to store logic blocks, logicfabric, data, etc. in lookup-tables (LUTs) and the like.

The baseband circuitry 710 may be implemented, for example, as asolder-down substrate including one or more integrated circuits, asingle packaged integrated circuit soldered to a main circuit board or amulti-chip module containing two or more integrated circuits. Althoughnot shown, baseband circuitry 710 may comprise one or more digitalbaseband systems, which may be coupled via an interconnect subsystem toa CPU subsystem, an audio subsystem, and an interface subsystem. Thedigital baseband subsystems may also be coupled to a digital basebandinterface and a mixed-signal baseband sub-system via anotherinterconnect subsystem. Each of the interconnect subsystems may includea bus system, point-to-point connections, network-on-chip (NOC)structures, and/or some other suitable bus or interconnect technology,such as those discussed herein. The audio sub-system may include digitalsignal processing circuitry, buffer memory, program memory, speechprocessing accelerator circuitry, data converter circuitry such asanalog-to-digital and digital-to-analog converter circuitry, analogcircuitry including one or more of amplifiers and filters, and/or otherlike components. In an aspect of the present disclosure, basebandcircuitry 710 may include protocol processing circuitry with one or moreinstances of control circuitry (not shown) to provide control functionsfor the digital baseband circuitry and/or radio frequency circuitry (forexample, the radio front end modules 715).

User interface circuitry 750 may include one or more user interfacesdesigned to enable user interaction with the system 700 or peripheralcomponent interfaces designed to enable peripheral component interactionwith the system 700. User interfaces may include, but are not limited toone or more physical or virtual buttons (e.g., a reset button), one ormore indicators (e.g., light emitting diodes (LEDs)), a physicalkeyboard or keypad, a mouse, a touchpad, a touchscreen, speakers orother audio emitting devices, microphones, a printer, a scanner, aheadset, a display screen or display device, etc. Peripheral componentinterfaces may include, but are not limited to, a non-volatile memoryport, a universal serial bus (USB) port, an audio jack, a power supplyinterface, etc.

The radio front end modules (RFEMs) 715 may comprise a millimeter waveRFEM and one or more sub-millimeter wave radio frequency integratedcircuits (RFICs). In some implementations, the one or moresub-millimeter wave RFICs may be physically separated from themillimeter wave RFEM. The RFICs may include connections to one or moreantennas or antenna arrays, and the RFEM may be connected to multipleantennas. In alternative implementations, both millimeter wave andsub-millimeter wave radio functions may be implemented in the samephysical radio front end module 715. The RFEMs 715 may incorporate bothmillimeter wave antennas and sub-millimeter wave antennas.

The memory circuitry 720 may include one or more of volatile memoryincluding dynamic random access memory (DRAM) and/or synchronous dynamicrandom access memory (SDRAM), and nonvolatile memory (NVM) includinghigh-speed electrically erasable memory (commonly referred to as Flashmemory), phase change random access memory (PRAM), magnetoresistiverandom access memory (MRAM), etc., and may incorporate thethree-dimensional (3D) cross-point (XPOINT) memories from Intel® andMicron®. Memory circuitry 720 may be implemented as one or more ofsolder down packaged integrated circuits, socketed memory modules andplug-in memory cards.

The PMIC 725 may include voltage regulators, surge protectors, poweralarm detection circuitry, and one or more backup power sources such asa battery or capacitor. The power alarm detection circuitry may detectone or more of brown out (under-voltage) and surge (over-voltage)conditions. The power tee circuitry 730 may provide for electrical powerdrawn from a network cable to provide both power supply and dataconnectivity to the infrastructure equipment 700 using a single cable.

The network controller circuitry 735 may provide connectivity to anetwork using a standard network interface protocol such as Ethernet,Ethernet over GRE Tunnels, Ethernet over Multiprotocol Label Switching(MPLS), or some other suitable protocol. Network connectivity may beprovided to/from the infrastructure equipment 700 via network interfaceconnector 740 using a physical connection, which may be electrical(commonly referred to as a “copper interconnect”), optical, or wireless.The network controller circuitry 735 may include one or more dedicatedprocessors and/or FPGAs to communicate using one or more of theaforementioned protocol. In some implementations, the network controllercircuitry 735 may include multiple controllers to provide connectivityto other networks using the same or different protocols.

The positioning circuitry 745, which may include circuitry to receiveand decode signals transmitted by one or more navigation satelliteconstellations of a global navigation satellite system (GNSS). Examplesof navigation satellite constellations (or GNSS) may include UnitedStates' Global Positioning System (GPS), Russia's Global NavigationSystem (GLONASS), the European Union's Galileo system, China's BeiDouNavigation Satellite System, a regional navigation system or GNSSaugmentation system (e.g., Navigation with Indian Constellation (NAVIC),Japan's Quasi-Zenith Satellite System (QZSS), France's DopplerOrbitography and Radio-positioning Integrated by Satellite (DORIS),etc.), or the like. The positioning circuitry 745 may comprise varioushardware elements (e.g., including hardware devices such as switches,filters, amplifiers, antenna elements, and the like to facilitate thecommunications over-the-air (OTA) communications) to communicate withcomponents of a positioning network, such as navigation satelliteconstellation nodes.

Nodes or satellites of the navigation satellite constellation(s) (“GNSSnodes”) may provide positioning services by continuously transmitting orbroadcasting GNSS signals along a line of sight, which may be used byGNSS receivers (e.g., positioning circuitry 745 and/or positioningcircuitry implemented by UEs 501, 502, or the like) to determine theirGNSS position. The GNSS signals may include a pseudorandom code (e.g., asequence of ones and zeros) that is known to the GNSS receiver and amessage that includes a time of transmission (ToT) of a code epoch(e.g., a defined point in the pseudorandom code sequence) and the GNSSnode position at the ToT. The GNSS receivers may monitor/measure theGNSS signals transmitted/broadcasted by a plurality of GNSS nodes (e.g.,four or more satellites) and solve various equations to determine acorresponding GNSS position (e.g., a spatial coordinate). The GNSSreceivers also implement clocks that are typically less stable and lessprecise than the atomic clocks of the GNSS nodes, and the GNSS receiversmay use the measured GNSS signals to determine the GNSS receivers'deviation from true time (e.g., an offset of the GNSS receiver clockrelative to the GNSS node time). In some embodiments, the positioningcircuitry 745 may include a Micro-Technology for Positioning,Navigation, and Timing (Micro-PNT) IC that uses a master timing clock toperform position tracking/estimation without GNSS assistance.

The GNSS receivers may measure the time of arrivals (ToAs) of the GNSSsignals from the plurality of GNSS nodes according to its own clock. TheGNSS receivers may determine ToF values for each received GNSS signalfrom the ToAs and the ToTs, and then may determine, from the ToFs, athree-dimensional (3D) position and clock deviation. The 3D position maythen be converted into a latitude, longitude and altitude. Thepositioning circuitry 745 may provide data to application circuitry 705which may include one or more of position data or time data. Applicationcircuitry 705 may use the time data to synchronize operations with otherradio base stations (e.g., RAN nodes 511, 512, 611 or the like).

The components shown by FIG. 7 may communicate with one another usinginterface circuitry. As used herein, the term “interface circuitry” mayrefer to, is part of, or includes circuitry providing for the exchangeof information between two or more components or devices. The term“interface circuitry” may refer to one or more hardware interfaces, forexample, buses, input/output (I/O) interfaces, peripheral componentinterfaces, network interface cards, and/or the like. Any suitable bustechnology may be used in various implementations, which may include anynumber of technologies, including industry standard architecture (ISA),extended ISA (EISA), peripheral component interconnect (PCI), peripheralcomponent interconnect extended (PCIx), PCI express (PCIe), or anynumber of other technologies. The bus may be a proprietary bus, forexample, used in a SoC based system. Other bus systems may be included,such as an I2C interface, an SPI interface, point to point interfaces,and a power bus, among others.

FIG. 8 illustrates an example of a platform 800 (or “device 800”) inaccordance with various embodiments. In embodiments, the computerplatform 800 may be suitable for use as UEs 501, 502, 601, applicationservers 530, and/or any other element/device discussed herein. Theplatform 800 may include any combinations of the components shown in theexample. The components of platform 800 may be implemented as integratedcircuits (ICs), portions thereof, discrete electronic devices, or othermodules, logic, hardware, software, firmware, or a combination thereofadapted in the computer platform 800, or as components otherwiseincorporated within a chassis of a larger system. The block diagram ofFIG. 8 is intended to show a high level view of components of thecomputer platform 800. However, some of the components shown may beomitted, additional components may be present, and different arrangementof the components shown may occur in other implementations.

The application circuitry 805 may include circuitry such as, but notlimited to single-core or multi-core processors and one or more of cachememory, low drop-out voltage regulators (LDOs), interrupt controllers,serial interfaces such as serial peripheral interface (SPI),inter-integrated circuit (I2C) or universal programmable serialinterface circuit, real time clock (RTC), timer-counters includinginterval and watchdog timers, general purpose input-output (IO), memorycard controllers such as secure digital/multi-media card (SD/MMC) orsimilar, universal serial bus (USB) interfaces, mobile industryprocessor interface (MIPI) interfaces and Joint Test Access Group (JTAG)test access ports. The processor(s) may include any combination ofgeneral-purpose processors and/or dedicated processors (e.g., graphicsprocessors, application processors, etc.). The processors (or cores) maybe coupled with or may include memory/storage and may be configured toexecute instructions stored in the memory/storage to enable variousapplications or operating systems to run on the platform 800. In someembodiments, processors of application circuitry 705/805 may process IPdata packets received from an EPC or 5GC.

Application circuitry 805 be or include a microprocessor, a multi-coreprocessor, a multithreaded processor, an ultra-low voltage processor, anembedded processor, or other known processing element. In one example,the application circuitry 805 may include an Intel® Architecture Core™based processor, such as a Quark™, an Atom™, an i3, an i5, an i7, or anMCU-class processor, or another such processor available from Intel®Corporation, Santa Clara, Calif. The processors of the applicationcircuitry 805 may also be one or more of Advanced Micro Devices (AMD)Ryzen® processor(s) or Accelerated Processing Units (APUs); A5-A9processor(s) from Apple® Inc., Snapdragon™ processor(s) from Qualcomm®Technologies, Inc., Texas Instruments, Inc.® Open MultimediaApplications Platform (OMAP)™ processor(s); a MIPS-based design fromMIPS Technologies, Inc; an ARM-based design licensed from ARM Holdings,Ltd.; or the like. In some implementations, the application circuitry805 may be a part of a system on a chip (SoC) in which the applicationcircuitry 805 and other components are formed into a single integratedcircuit, or a single package, such as the Edison™ or Galileo™ SoC boardsfrom Intel® Corporation.

Additionally or alternatively, application circuitry 805 may includecircuitry such as, but not limited to, one or more a field-programmabledevices (FPDs) such as FPGAs and the like; programmable logic devices(PLDs) such as complex PLDs (CPLDs), high-capacity PLDs (HCPLDs), andthe like; ASICs such as structured ASICs and the like; programmable SoCs(PSoCs); and the like. In such embodiments, the circuitry of applicationcircuitry 805 may comprise logic blocks or logic fabric including andother interconnected resources that may be programmed to perform variousfunctions, such as the procedures, methods, functions, etc. of thevarious embodiments discussed herein. In such embodiments, the circuitryof application circuitry 805 may include memory cells (e.g., erasableprogrammable read-only memory (EPROM), electrically erasableprogrammable read-only memory (EEPROM), flash memory, static memory(e.g., static random access memory (SRAM), anti-fuses, etc.) used tostore logic blocks, logic fabric, data, etc. in lookup-tables (LUTs) andthe like.

The baseband circuitry 820 may be implemented, for example, as asolder-down substrate including one or more integrated circuits, asingle packaged integrated circuit soldered to a main circuit board or amulti-chip module containing two or more integrated circuits. Althoughnot shown, baseband circuitry 800 may comprise one or more digitalbaseband systems, which may be coupled via an interconnect subsystem toa CPU subsystem, an audio subsystem, and an interface subsystem. Thedigital baseband subsystems may also be coupled to a digital basebandinterface and a mixed-signal baseband sub-system via anotherinterconnect subsystem. Each of the interconnect subsystems may includea bus system, point-to-point connections, network-on-chip (NOC)structures, and/or some other suitable bus or interconnect technology,such as those discussed herein. The audio sub-system may include digitalsignal processing circuitry, buffer memory, program memory, speechprocessing accelerator circuitry, data converter circuitry such asanalog-to-digital and digital-to-analog converter circuitry, analogcircuitry including one or more of amplifiers and filters, and/or otherlike components. In an aspect of the present disclosure, basebandcircuitry 820 may include protocol processing circuitry with one or moreinstances of control circuitry (not shown) to provide control functionsfor the digital baseband circuitry and/or radio frequency circuitry (forexample, the radio front end modules 1215).

The radio front end modules (RFEMs) 815 may comprise a millimeter waveRFEM and one or more sub-millimeter wave radio frequency integratedcircuits (RFICs). In some implementations, the one or moresub-millimeter wave RFICs may be physically separated from themillimeter wave RFEM. The RFICs may include connections to one or moreantennas or antenna arrays, and the RFEM may be connected to multipleantennas. In alternative implementations, both millimeter wave andsub-millimeter wave radio functions may be implemented in the samephysical radio front end module 815. The RFEMs 815 may incorporate bothmillimeter wave antennas and sub-millimeter wave antennas.

The memory circuitry 820 may include any number and type of memorydevices used to provide for a given amount of system memory. Asexamples, the memory circuitry 820 may include one or more of volatilememory including be random access memory (RAM), dynamic RAM (DRAM)and/or synchronous dynamic RAM (SDRAM), and nonvolatile memory (NVM)including high-speed electrically erasable memory (commonly referred toas Flash memory), phase change random access memory (PRAM),magnetoresistive random access memory (MRAM), etc. The memory circuitry820 may be developed in accordance with a Joint Electron DevicesEngineering Council (JEDEC) low power double data rate (LPDDR)-baseddesign, such as LPDDR2, LPDDR3, LPDDR4, or the like. Memory circuitry720 may be implemented as one or more of solder down packaged integratedcircuits, single die package (SDP), dual die package (DDP) or quad diepackage (Q17P), socketed memory modules, dual inline memory modules(DIMMs) including microDIMMs or MiniDIMMs, and/or soldered onto amotherboard via a ball grid array (BGA). In low power implementations,the memory circuitry 820 may be on-die memory or registers associatedwith the application circuitry 805. To provide for persistent storage ofinformation such as data, applications, operating systems and so forth,memory circuitry 820 may include one or more mass storage devices, whichmay include, inter alia, a solid state disk drive (SSDD), hard diskdrive (HDD), a micro HDD, resistance change memories, phase changememories, holographic memories, or chemical memories, among others. Forexample, the computer platform 800 may incorporate the three-dimensional(3D) cross-point (XPOINT) memories from Intel® and Micron®.

Removable memory circuitry 823 may include devices, circuitry,enclosures/housings, ports or receptacles, etc. used to coupled portabledata storage devices with the platform 800. These portable data storagedevices may be used for mass storage purposes, and may include, forexample, flash memory cards (e.g., Secure Digital (SD) cards, microSDcards, xD picture cards, and the like), and USB flash drives, opticaldiscs, eternal HDDs, and the like.

The platform 800 may also include interface circuitry (not shown) thatis used to connect eternal devices with the platform 800. The externaldevices connected to the platform 800 via the interface circuitry mayinclude sensors 821, such as accelerometers, level sensors, flowsensors, temperature sensors, pressure sensors, barometric pressuresensors, and the like. The interface circuitry may be used to connectthe platform 800 to electro-mechanical components (EMCs) 822, which mayallow platform 800 to change its state, position, and/or orientation, ormove or control a mechanism or system. The EMCs 822 may include one ormore power switches, relays including electromechanical relays (EMRs)and/or solid state relays (SSRs), actuators (e.g., valve actuators,etc.), an audible sound generator, a visual warning device, motors(e.g., DC motors, stepper motors, etc.), wheels, thrusters, propellers,claws, clamps, hooks, and/or other like electro-mechanical components.In embodiments, platform 800 may be configured to operate one or moreEMCs 822 based on one or more captured events and/or instructions orcontrol signals received from a service provider and/or various clients.

In some implementations, the interface circuitry may connect theplatform 800 with positioning circuitry 845, which may be the same orsimilar as the positioning circuitry 845 discussed with regard to FIG.7.

In some implementations, the interface circuitry may connect theplatform 800 with near-field communication (NFC) circuitry 840, whichmay include an NFC controller coupled with an antenna element and aprocessing device. The NFC circuitry 840 may be configured to readelectronic tags and/or connect with another NFC-enabled device.

The driver circuitry 846 may include software and hardware elements thatoperate to control particular devices that are embedded in the platform800, attached to the platform 800, or otherwise communicatively coupledwith the platform 800. The driver circuitry 846 may include individualdrivers allowing other components of the platform 800 to interact orcontrol various input/output (I/O) devices that may be present within,or connected to, the platform 800. For example, driver circuitry 846 mayinclude a display driver to control and allow access to a displaydevice, a touchscreen driver to control and allow access to atouchscreen interface of the platform 800, sensor drivers to obtainsensor readings of sensors 821 and control and allow access to sensors821, EMC drivers to obtain actuator positions of the EMCs 822 and/orcontrol and allow access to the EMCs 822, a camera driver to control andallow access to an embedded image capture device, audio drivers tocontrol and allow access to one or more audio devices.

The power management integrated circuitry (PMIC) 825 (also referred toas “power management circuitry 825”) may manage power provided tovarious components of the platform 800. In particular, with respect tothe baseband circuitry 820, the PMIC 825 may control power-sourceselection, voltage scaling, battery charging, or DC-to-DC conversion.The PMIC 825 may often be included when the platform 800 is capable ofbeing powered by a battery 830, for example, when the device is includedin a UE 501, 502, 601.

In some embodiments, the PMIC 825 may control, or otherwise be part of,various power saving mechanisms of the platform 800. For example, if theplatform 800 is in an RRC_Connected state, where it is still connectedto the RAN node as it expects to receive traffic shortly, then it mayenter a state known as Discontinuous Reception Mode (DRX) after a periodof inactivity. During this state, the platform 800 may power down forbrief intervals of time and thus save power. If there is no data trafficactivity for an extended period of time, then the platform 800 maytransition off to an RRC_Idle state, where it disconnects from thenetwork and does not perform operations such as channel qualityfeedback, handover, etc. The platform 800 goes into a very low powerstate and it performs paging where again it periodically wakes up tolisten to the network and then powers down again. The platform 800 maynot receive data in this state, in order to receive data, it musttransition back to RRC_Connected state. An additional power saving modemay allow a device to be unavailable to the network for periods longerthan a paging interval (ranging from seconds to a few hours). Duringthis time, the device is totally unreachable to the network and maypower down completely. Any data sent during this time incurs a largedelay and it is assumed the delay is acceptable.

A battery 830 may power the platform 800, although in some examples theplatform 800 may be mounted deployed in a fixed location, and may have apower supply coupled to an electrical grid. The battery 830 may be alithium ion battery, a metal-air battery, such as a zinc-air battery, analuminum-air battery, a lithium-air battery, and the like. In someimplementations, such as in V2X applications, the battery 830 may be atypical lead-acid automotive battery.

In some implementations, the battery 830 may be a “smart battery,” whichincludes or is coupled with a Battery Management System (BMS) or batterymonitoring integrated circuitry. The BMS may be included in the platform800 to track the state of charge (SoCh) of the battery 830. The BMS maybe used to monitor other parameters of the battery 830 to providefailure predictions, such as the state of health (SoH) and the state offunction (SoF) of the battery 830. The BMS may communicate theinformation of the battery 830 to the application circuitry 805 or othercomponents of the platform 800. The BMS may also include ananalog-to-digital (ADC) convertor that allows the application circuitry805 to directly monitor the voltage of the battery 830 or the currentflow from the battery 830. The battery parameters may be used todetermine actions that the platform 800 may perform, such astransmission frequency, network operation, sensing frequency, and thelike.

A power block, or other power supply coupled to an electrical grid maybe coupled with the BMS to charge the battery 830. In some examples, thepower block 528 may be replaced with a wireless power receiver to obtainthe power wirelessly, for example, through a loop antenna in thecomputer platform 800. In these examples, a wireless battery chargingcircuit may be included in the BMS. The specific charging circuitschosen may depend on the size of the battery 830, and thus, the currentrequired. The charging may be performed using the Airfuel standardpromulgated by the Airfuel Alliance, the Qi wireless charging standardpromulgated by the Wireless Power Consortium, or the Rezence chargingstandard, promulgated by the Alliance for Wireless Power, among others.

Although not shown, the components of platform 800 may communicate withone another using a suitable bus technology, which may include anynumber of technologies, including industry standard architecture (ISA),extended ISA (EISA), peripheral component interconnect (PCI), peripheralcomponent interconnect extended (PCIx), PCI express (PCIe), aTime-Trigger Protocol (TTP) system, or a Fle10ay system, or any numberof other technologies. The bus may be a proprietary bus, for example,used in a SoC based system. Other bus systems may be included, such asan I2C interface, an SPI interface, point to point interfaces, and apower bus, among others.

FIG. 13 illustrates example components of baseband circuitry 710/810 andradio front end modules (RFEM) 715/815 in accordance with someembodiments. As shown, the RFEM 715/815 may include Radio Frequency (RF)circuitry 1306, front-end module (FEM) circuitry 908, one or moreantennas 920 coupled together at least as shown.

The baseband circuitry 710/810 may include circuitry such as, but notlimited to, one or more single-core or multi-core processors. Thebaseband circuitry 710/810 may include one or more baseband processorsor control logic to process baseband signals received from a receivesignal path of the RF circuitry 906 and to generate baseband signals fora transmit signal path of the RF circuitry 906. Baseband processingcircuity 710/80 may interface with the application circuitry 705/805 forgeneration and processing of the baseband signals and for controllingoperations of the RF circuitry 906. For example, in some embodiments,the baseband circuitry 710/80 may include a third generation (3G)baseband processor 904A, a fourth generation (4G) baseband processor904B, a fifth generation (5G) baseband processor 904C, or other basebandprocessor(s) 904D for other existing generations, generations indevelopment or to be developed in the future (e.g., second generation(2G), sixth generation (6G), etc.). The baseband circuitry 710/810(e.g., one or more of baseband processors 904A-D) may handle variousradio control functions that enable communication with one or more radionetworks via the RF circuitry 906. In other embodiments, some or all ofthe functionality of baseband processors 904A-D may be included inmodules stored in the memory 904G and executed via a Central ProcessingUnit (CPU) 904E. The radio control functions may include, but are notlimited to, signal modulation/demodulation, encoding/decoding, radiofrequency shifting, etc. In some embodiments, modulation/demodulationcircuitry of the baseband circuitry 710/810 may include Fast-FourierTransform (FFT), precoding, or constellation mapping/demappingfunctionality. In some embodiments, encoding/decoding circuitry of thebaseband circuitry 710/810 may include convolution, tail-bitingconvolution, turbo, Viterbi, or Low Density Parity Check (LDPC)encoder/decoder functionality. Embodiments of modulation/demodulationand encoder/decoder functionality are not limited to these examples andmay include other suitable functionality in other embodiments.

In some embodiments, the baseband circuitry 710/810 may include one ormore audio digital signal processor(s) (DSP) 904F. The audio DSP(s) 904Fmay be include elements for compression/decompression and echocancellation and may include other suitable processing elements in otherembodiments. Components of the baseband circuitry may be suitablycombined in a single chip, a single chipset, or disposed on a samecircuit board in some embodiments. In some embodiments, some or all ofthe constituent components of the baseband circuitry 710/810 and theapplication circuitry 705/805 may be implemented together such as, forexample, on a system on a chip (SOC).

In some embodiments, the baseband circuitry 710/810 may provide forcommunication compatible with one or more radio technologies. Forexample, in some embodiments, the baseband circuitry 710/810 may supportcommunication with an evolved universal terrestrial radio access network(EUTRAN) or other wireless metropolitan area networks (WMAN), a wirelesslocal area network (WLAN), a wireless personal area network (WPAN).Embodiments in which the baseband circuitry 710/810 is configured tosupport radio communications of more than one wireless protocol may bereferred to as multi-mode baseband circuitry.

RF circuitry 906 may enable communication with wireless networks usingmodulated electromagnetic radiation through a non-solid medium. Invarious embodiments, the RF circuitry 906 may include switches, filters,amplifiers, etc. to facilitate the communication with the wirelessnetwork. RF circuitry 906 may include a receive signal path which mayinclude circuitry to down-convert RF signals received from the FEMcircuitry 808 and provide baseband signals to the baseband circuitry710/810. RF circuitry 906 may also include a transmit signal path whichmay include circuitry to up-convert baseband signals provided by thebaseband circuitry 710/810 and provide RF output signals to the FEMcircuitry 808 for transmission.

In some embodiments, the receive signal path of the RF circuitry 906 mayinclude mixer circuitry 906 a, amplifier circuitry 906 b and filtercircuitry 906 c. In some embodiments, the transmit signal path of the RFcircuitry 906 may include filter circuitry 906 c and mixer circuitry 906a. RF circuitry 906 may also include synthesizer circuitry 906 d forsynthesizing a frequency for use by the mixer circuitry 906 a of thereceive signal path and the transmit signal path. In some embodiments,the mixer circuitry 906 a of the receive signal path may be configuredto down-convert RF signals received from the FEM circuitry 808 based onthe synthesized frequency provided by synthesizer circuitry 906 d. Theamplifier circuitry 906 b may be configured to amplify thedown-converted signals and the filter circuitry 906 c may be a low-passfilter (LPF) or band-pass filter (BPF) configured to remove unwantedsignals from the down-converted signals to generate output basebandsignals. Output baseband signals may be provided to the basebandcircuitry 710/810 for further processing. In some embodiments, theoutput baseband signals may be zero-frequency baseband signals, althoughthis is not a requirement. In some embodiments, mixer circuitry 906 a ofthe receive signal path may comprise passive mixers, although the scopeof the embodiments is not limited in this respect.

In some embodiments, the mixer circuitry 906 a of the transmit signalpath may be configured to up-convert input baseband signals based on thesynthesized frequency provided by the synthesizer circuitry 906 d togenerate RF output signals for the FEM circuitry 908. The basebandsignals may be provided by the baseband circuitry 710/810 and may befiltered by filter circuitry 906 c.

In some embodiments, the mixer circuitry 906 a of the receive signalpath and the mixer circuitry 906 a of the transmit signal path mayinclude two or more mixers and may be arranged for quadraturedownconversion and upconversion, respectively. In some embodiments, themixer circuitry 906 a of the receive signal path and the mixer circuitry906 a of the transmit signal path may include two or more mixers and maybe arranged for image rejection (e.g., Hartley image rejection). In someembodiments, the mixer circuitry 906 a of the receive signal path andthe mixer circuitry 906 a may be arranged for direct downconversion anddirect upconversion, respectively. In some embodiments, the mixercircuitry 906 a of the receive signal path and the mixer circuitry 906 aof the transmit signal path may be configured for super-heterodyneoperation.

In some embodiments, the output baseband signals and the input basebandsignals may be analog baseband signals, although the scope of theembodiments is not limited in this respect. In some alternateembodiments, the output baseband signals and the input baseband signalsmay be digital baseband signals. In these alternate embodiments, the RFcircuitry 906 may include analog-to-digital converter (ADC) anddigital-to-analog converter (DAC) circuitry and the baseband circuitry710/810 may include a digital baseband interface to communicate with theRF circuitry 906.

In some dual-mode embodiments, a separate radio IC circuitry may beprovided for processing signals for each spectrum, although the scope ofthe embodiments is not limited in this respect.

In some embodiments, the synthesizer circuitry 906 d may be afractional-N synthesizer or a fractional N/N+1 synthesizer, although thescope of the embodiments is not limited in this respect as other typesof frequency synthesizers may be suitable. For example, synthesizercircuitry 906 d may be a delta-sigma synthesizer, a frequencymultiplier, or a synthesizer comprising a phase-locked loop with afrequency divider.

The synthesizer circuitry 906 d may be configured to synthesize anoutput frequency for use by the mixer circuitry 906 a of the RFcircuitry 906 based on a frequency input and a divider control input. Insome embodiments, the synthesizer circuitry 906 d may be a fractionalN/N+1 synthesizer.

In some embodiments, frequency input may be provided by a voltagecontrolled oscillator (VCO), although that is not a requirement. Dividercontrol input may be provided by either the baseband circuitry 710/810or the applications processor 705/805 depending on the desired outputfrequency. In some embodiments, a divider control input (e.g., N) may bedetermined from a look-up table based on a channel indicated by theapplications processor 705/805.

Synthesizer circuitry 906 d of the RF circuitry 906 may include adivider, a delay-locked loop (DLL), a multiplexer and a phaseaccumulator. In some embodiments, the divider may be a dual modulusdivider (DMD) and the phase accumulator may be a digital phaseaccumulator (DPA). In some embodiments, the DMD may be configured todivide the input signal by either N or N+1 (e.g., based on a carry out)to provide a fractional division ratio. In some example embodiments, theDLL may include a set of cascaded, tunable, delay elements, a phasedetector, a charge pump and a D-type flip-flop. In these embodiments,the delay elements may be configured to break a VCO period up into Ndequal packets of phase, where Nd is the number of delay elements in thedelay line. In this way, the DLL provides negative feedback to helpensure that the total delay through the delay line is one VCO cycle.

In some embodiments, synthesizer circuitry 906 d may be configured togenerate a carrier frequency as the output frequency, while in otherembodiments, the output frequency may be a multiple of the carrierfrequency (e.g., twice the carrier frequency, four times the carrierfrequency) and used in conjunction with quadrature generator and dividercircuitry to generate multiple signals at the carrier frequency withmultiple different phases with respect to each other. In someembodiments, the output frequency may be a LO frequency (fLO). In someembodiments, the RF circuitry 906 may include an IQ/polar converter.

FEM circuitry 908 may include a receive signal path which may includecircuitry configured to operate on RF signals received from one or moreantennas 920, amplify the received signals and provide the amplifiedversions of the received signals to the RF circuitry 906 for furtherprocessing. FEM circuitry 908 may also include a transmit signal pathwhich may include circuitry configured to amplify signals fortransmission provided by the RF circuitry 906 for transmission by one ormore of the one or more antennas 920. In various embodiments, theamplification through the transmit or receive signal paths may be donesolely in the RF circuitry 906, solely in the FEM 908, or in both the RFcircuitry 906 and the FEM 908.

In some embodiments, the FEM circuitry 908 may include a TX/RX switch toswitch between transmit mode and receive mode operation. The FEMcircuitry may include a receive signal path and a transmit signal path.The receive signal path of the FEM circuitry may include an LNA toamplify received RF signals and provide the amplified received RFsignals as an output (e.g., to the RF circuitry 906). The transmitsignal path of the FEM circuitry 908 may include a power amplifier (PA)to amplify input RF signals (e.g., provided by RF circuitry 906), andone or more filters to generate RF signals for subsequent transmission(e.g., by one or more of the one or more antennas 920).

Processors of the application circuitry 705/805 and processors of thebaseband circuitry 710/810 may be used to execute elements of one ormore instances of a protocol stack. For example, processors of thebaseband circuitry 710/810, alone or in combination, may be used executeLayer 3, Layer 2, or Layer 1 functionality, while processors of thebaseband circuitry 710/810 may utilize data (e.g., packet data) receivedfrom these layers and further execute Layer 4 functionality (e.g.,transmission communication protocol (TCP) and user datagram protocol(UDP) layers). As referred to herein, Layer 3 may comprise a radioresource control (RRC) layer, described in further detail below. Asreferred to herein, Layer 2 may comprise a medium access control (MAC)layer, a radio link control (RLC) layer, and a packet data convergenceprotocol (PDCP) layer, described in further detail below. As referred toherein, Layer 1 may comprise a physical (PHY) layer of a UE/RAN node,described in further detail below.

FIG. 10 illustrates example interfaces of baseband circuitry inaccordance with some embodiments. As discussed above, the basebandcircuitry 710/810 of FIGS. 7-8 may comprise processors 804A-804E and amemory 904G utilized by said processors. Each of the processors904A-904E may include a memory interface, 1004A-1004E, respectively, tosend/receive data to/from the memory 904G.

The baseband circuitry 710/810 may further include one or moreinterfaces to communicatively couple to other circuitries/devices, suchas a memory interface 1012 (e.g., an interface to send/receive datato/from memory external to the baseband circuitry 710/1210), anapplication circuitry interface 1014 (e.g., an interface to send/receivedata to/from the application circuitry 705/805 of FIGS. 7-8), an RFcircuitry interface 1016 (e.g., an interface to send/receive datato/from RF circuitry 906 of FIG. 9), a wireless hardware connectivityinterface 1018 (e.g., an interface to send/receive data to/from NearField Communication (NFC) components, Bluetooth® components (e.g.,Bluetooth® Low Energy), Wi-Fi® components, and other communicationcomponents), and a power management interface 1020 (e.g., an interfaceto send/receive power or control signals to/from the PMIC 825.

FIG. 11 is an illustration of a control plane protocol stack inaccordance with some embodiments. In this embodiment, a control plane1100 is shown as a communications protocol stack between the UE 501 (oralternatively, the UE 502), the RAN node 511 (or alternatively, the RANnode 512), and the MME 521.

The PHY layer 1101 may transmit or receive information used by the MAClayer 1102 over one or more air interfaces. The PHY layer 1101 mayfurther perform link adaptation or adaptive modulation and coding (AMC),power control, cell search (e.g., for initial synchronization andhandover purposes), and other measurements used by higher layers, suchas the RRC layer 1105. The PHY layer 1101 may still further performerror detection on the transport channels, forward error correction(FEC) coding/decoding of the transport channels, modulation/demodulationof physical channels, interleaving, rate matching, mapping onto physicalchannels, and Multiple Input Multiple Output (MIMO) antenna processing.

The MAC layer 1102 may perform mapping between logical channels andtransport channels, multiplexing of MAC service data units (SDUs) fromone or more logical channels onto transport blocks (TB) to be deliveredto PHY via transport channels, de-multiplexing MAC SDUs to one or morelogical channels from transport blocks (TB) delivered from the PHY viatransport channels, multiplexing MAC SDUs onto TBs, schedulinginformation reporting, error correction through hybrid automatic repeatrequest (HARQ), and logical channel prioritization.

The RLC layer 1103 may operate in a plurality of modes of operation,including: Transparent Mode™, Unacknowledged Mode (UM), and AcknowledgedMode (AM). The RLC layer 1103 may execute transfer of upper layerprotocol data units (PDUs), error correction through automatic repeatrequest (ARQ) for AM data transfers, and concatenation, segmentation andreassembly of RLC SDUs for UM and AM data transfers. The RLC layer 1103may also execute re-segmentation of RLC data PDUs for AM data transfers,reorder RLC data PDUs for UM and AM data transfers, detect duplicatedata for UM and AM data transfers, discard RLC SDUs for UM and AM datatransfers, detect protocol errors for AM data transfers, and perform RLCre-establishment.

The PDCP layer 1104 may execute header compression and decompression ofIP data, maintain PDCP Sequence Numbers (SNs), perform in-sequencedelivery of upper layer PDUs at re-establishment of lower layers,eliminate duplicates of lower layer SDUs at re-establishment of lowerlayers for radio bearers mapped on RLC AM, cipher and decipher controlplane data, perform integrity protection and integrity verification ofcontrol plane data, control timer-based discard of data, and performsecurity operations (e.g., ciphering, deciphering, integrity protection,integrity verification, etc.).

The main services and functions of the RRC layer 1105 may includebroadcast of system information (e.g., included in Master InformationBlocks (MIBs) or System Information Blocks (SIBs) related to thenon-access stratum (NAS)), broadcast of system information related tothe access stratum (AS), paging, establishment, maintenance and releaseof an RRC connection between the UE and E-UTRAN (e.g., RRC connectionpaging, RRC connection establishment, RRC connection modification, andRRC connection release), establishment, configuration, maintenance andrelease of point to point Radio Bearers, security functions includingkey management, inter radio access technology (RAT) mobility, andmeasurement configuration for UE measurement reporting. Said MIBs andSIBs may comprise one or more information elements (IEs), which may eachcomprise individual data fields or data structures.

The UE 501 and the RAN node 511 may utilize a Uu interface (e.g., anLTE-Uu interface) to exchange control plane data via a protocol stackcomprising the PHY layer 1101, the MAC layer 1102, the RLC layer 1103,the PDCP layer 1104, and the RRC layer 1105.

The non-access stratum (NAS) protocols 1106 form the highest stratum ofthe control plane between the UE 501 and the MME 521. The NAS protocols1106 support the mobility of the UE 501 and the session managementprocedures to establish and maintain IP connectivity between the UE 501and the P-GW 523.

The S1 Application Protocol (S1-AP) layer 1115 may support the functionsof the S1 interface and comprise Elementary Procedures (EPs). An EP is aunit of interaction between the RAN node 511 and the CN 520. The S1-APlayer services may comprise two groups: UE-associated services and nonUE-associated services. These services perform functions including, butnot limited to: E-UTRAN Radio Access Bearer (E-RAB) management, UEcapability indication, mobility, NAS signaling transport, RANInformation Management (RIM), and configuration transfer.

The Stream Control Transmission Protocol (SCTP) layer (alternativelyreferred to as the SCTP/IP layer) 1114 may ensure reliable delivery ofsignaling messages between the RAN node 511 and the MME 521 based, inpart, on the IP protocol, supported by the IP layer 1113. The L2 layer1112 and the L1 layer 1111 may refer to communication links (e.g., wiredor wireless) used by the RAN node and the MME to exchange information.

The RAN node 511 and the MME 521 may utilize an S1-MME interface toexchange control plane data via a protocol stack comprising the L1 layer1111, the L2 layer 1112, the IP layer 1113, the SCTP layer 1114, and theS1-AP layer 1115.

FIG. 12 is an illustration of a user plane protocol stack in accordancewith some embodiments. In this embodiment, a user plane 1200 is shown asa communications protocol stack between the UE 501 (or alternatively,the UE 502), the RAN node 511 (or alternatively, the RAN node 512), theS-GW 522, and the P-GW 523. The user plane 1200 may utilize at leastsome of the same protocol layers as the control plane 1500. For example,the UE 501 and the RAN node 511 may utilize a Uu interface (e.g., anLTE-Uu interface) to exchange user plane data via a protocol stackcomprising the PHY layer 1501, the MAC layer 1502, the RLC layer 1503,the PDCP layer 1504.

The General Packet Radio Service (GPRS) Tunneling Protocol for the userplane (GTP-U) layer 1204 may be used for carrying user data within theGPRS core network and between the radio access network and the corenetwork. The user data transported can be packets in any of IPv4, IPv6,or PPP formats, for example. The UDP and IP security (UDP/IP) layer 1203may provide checksums for data integrity, port numbers for addressingdifferent functions at the source and destination, and encryption andauthentication on the selected data flows. The RAN node 511 and the S-GW522 may utilize an S1-U interface to exchange user plane data via aprotocol stack comprising the L1 layer 1511, the L2 layer 1512, theUDP/IP layer 1203, and the GTP-U layer 1204. The S-GW 522 and the P-GW523 may utilize an S5/S8a interface to exchange user plane data via aprotocol stack comprising the L1 layer 1511, the L2 layer 1512, theUDP/IP layer 1203, and the GTP-U layer 1204. As discussed above withrespect to FIG. 15, NAS protocols support the mobility of the UE 501 andthe session management procedures to establish and maintain IPconnectivity between the UE 501 and the P-GW 523.

FIG. 13 is a block diagram illustrating components, according to someexample embodiments, able to read instructions from a machine-readableor computer-readable medium (e.g., a non-transitory machine-readablestorage medium) and perform any one or more of the methodologiesdiscussed herein. Specifically, FIG. 13 shows a diagrammaticrepresentation of hardware resources 1300 including one or moreprocessors (or processor cores) 1310, one or more memory/storage devices1320, and one or more communication resources 1330, each of which may becommunicatively coupled via a bus 1340. As used herein, the term“computing resource”, “hardware resource”, etc., may refer to a physicalor virtual device, a physical or virtual component within a computingenvironment, and/or physical or virtual component within a particulardevice, such as computer devices, mechanical devices, memory space,processor/CPU time and/or processor/CPU usage, processor and acceleratorloads, hardware time or usage, electrical power, input/outputoperations, ports or network sockets, channel/link allocation,throughput, memory usage, storage, network, database and applications,and/or the like. For embodiments where node virtualization (e.g., NFV)is utilized, a hypervisor 1302 may be executed to provide an executionenvironment for one or more network slices/sub-slices to utilize thehardware resources 1300. A “virtualized resource” may refer to compute,storage, and/or network resources provided by virtualizationinfrastructure to an application, device, system, etc.

The processors 1310 (e.g., a central processing unit (CPU), a reducedinstruction set computing (RISC) processor, a complex instruction setcomputing (CISC) processor, a graphics processing unit (GPU), a digitalsignal processor (DSP) such as a baseband processor, an applicationspecific integrated circuit (ASIC), a radio-frequency integrated circuit(RFIC), another processor, or any suitable combination thereof) mayinclude, for example, a processor 1312 and a processor 1314.

The memory/storage devices 1320 may include main memory, disk storage,or any suitable combination thereof. The memory/storage devices 1320 mayinclude, but are not limited to any type of volatile or non-volatilememory such as dynamic random access memory (DRAM), static random-accessmemory (SRAM), erasable programmable read-only memory (EPROM),electrically erasable programmable read-only memory (EEPROM), Flashmemory, solid-state storage, etc.

The communication resources 1330 may include interconnection or networkinterface components or other suitable devices to communicate with oneor more peripheral devices 1304 or one or more databases 1306 via anetwork 1308. For example, the communication resources 1330 may includewired communication components (e.g., for coupling via a UniversalSerial Bus (USB)), cellular communication components, NFC components,Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components,and other communication components. As used herein, the term “networkresource” or “communication resource” may refer to computing resourcesthat are accessible by computer devices via a communications network.The term “system resources” may refer to any kind of shared entities toprovide services, and may include computing and/or network resources.System resources may be considered as a set of coherent functions,network data objects or services, accessible through a server where suchsystem resources reside on a single host or multiple hosts and areclearly identifiable.

Instructions 1350 may comprise software, a program, an application, anapplet, an app, or other executable code for causing at least any of theprocessors 1310 to perform any one or more of the methodologiesdiscussed herein. The instructions 1350 may reside, completely orpartially, within at least one of the processors 1310 (e.g., within theprocessor's cache memory), the memory/storage devices 1320, or anysuitable combination thereof. Furthermore, any portion of theinstructions 1350 may be transferred to the hardware resources 1300 fromany combination of the peripheral devices 1304 or the databases 1306.Accordingly, the memory of processors 1310, the memory/storage devices1320, the peripheral devices 1304, and the databases 1306 are examplesof computer-readable and machine-readable media.

In some embodiments, the electronic device(s), network(s), system(s),chip(s) or component(s), or portions or implementations thereof, ofFIGS. 5-13, or some other figure herein may be configured to perform oneor more processes, techniques, or methods as described herein, orportions thereof. For example, the device of FIGS. 7, 8, and 13, andparticularly, the baseband circuitry of FIGS. 9 and 10, may beconfigured to implement one or more of the processes described herein(for example, the operation flows/algorithmic structures of FIGS. 3-4.

In some embodiments, the electronic device(s), network(s), system(s),chip(s) or component(s), or portions or implementations thereof, ofFIGS. 5-13, or some other figure herein, may be configured to performone or more processes, techniques, or methods as described herein, orportions thereof. Some processes are depicted in FIG. 3 and FIG. 4.

EXAMPLES

Example 1 may include method for new radio (NR) communications,comprising a method of configuring an UE with monitoring of new compactor size-matched DCI formats (referred to as DCI formats 0_2 and 1_2 forDL and UL scheduling respectively) or monitoring of optimized DCIformats 0_0/0_1 and 1_0/1_1, as part of the search space setconfiguration via UE-specific higher layer signaling.

Example 2 may include the method of example 1 and/or some other examplesherein, wherein the new compact DCI format has DCI payload size lowerthan the DCI formats 0_0/1_0 for a given UL and/or DL BWP sizes. Newsize-matched DCI format has DCI payload size that is matched to DCIformat 0_1 for UL scheduling and matched to DCI format 1_1 for DLscheduling, where these two new DL and UL DCI formats may not besize-matched between DL and UL formats.

Example 3 may include the method of example 1 and/or some other examplesherein, wherein the new DCI formats 0_2/1_2 are only introduced toenable new features and their corresponding signaling. If no new DCIfield is added, the existing fallback/non-fallback formats are used andtheir corresponding fields may be further optimized and re-interpreted.

Example 4 may include the method of example 1 and/or some other examplesherein, wherein the new fields may be added to DCI format 0_1 or 1_1 orboth, the presence of which fields and their bit-widths may depend onhigher layer configuration of related features.

Example 5 may include the method of example 1 and/or some other examplesherein, wherein the new DCI format is defined as an optional UEcapability.

Example 6 may include the method of example 1 and/or some other examplesherein, wherein for a UE supporting monitoring of the new compact orsize-matched DCI formats, a UE may be configured using UE-specifichigher layer signaling with possible monitoring of DCI formats 0_2 and1_2 first, before it may be configured to monitor for these new compactor size-matched DCI formats as part of search space set configuration.

Example 7 may include the method of example 1 and/or some other examplesherein, wherein for a UE supporting monitoring of the new compact orsize-matched DCI formats, the UE may be directly configured to monitorfor the new compact or size-matched DCI format as part of the searchspace set configuration via UE-specific higher layer signaling, withouta need to be first configured with separate UE-specific signaling.

Example 8 may include the method of example 1 and/or some other examplesherein, wherein the compact or size-matched DCI formats may only beconfigured for monitoring in a PDCCH UE-specific search space (USS).

Example 9 may include the method of example 1 and/or some other examplesherein, wherein the compact or size-matched DCI formats may beconfigured for monitoring in a PDCCH UE-specific search space or in acommon search space (CSS).

Example 10 may include the method of example 1 and/or some otherexamples herein, wherein the UE may be configured with monitoring ofeither of DCI format 0_2 or format 1_2 for UL or DL schedulingrespectively in a configured search space set, and for scheduling of theother link direction (for example, DL or UL respectively), thecorresponding “fallback DCI format”, for example, DCI format 1_0 and 0_0for DL and UL scheduling respectively, is assumed, and these two DCIformats are size-matched in a configured search space set.

Example 11 may include the method of example 1 and/or some otherexamples herein, wherein the compact or size-matched DCI formats 0_2/1_2are transmitted with CRC scrambled with either C-RNTI or CS-RNTI or ahigher layer-configured RNTI.

Example 12 may include the method of examples 8 or 9 and/or some otherexamples herein, wherein, if the compact or size-matched DCI format isconfigured for monitoring in a PDCCH USS, the higher layer fieldUSS-DCI-format is extended to 2-bit field to indicate choice between DCIformats: (i) 0_0/1_0; (ii) 0_1 & 1_1; and (iii) 0_2/1_2, with the fourthcode-point being reserved.

Example 13 may include the method of examples 8 or 9 and/or some otherexamples herein, wherein, if the compact or size-matched DCI format isconfigured for monitoring in a PDCCH USS, the higher layer fieldUSS-DCI-format is extended to 2-bit field to indicate choice between DCIformats: (i) 0_0/1_0; (ii) 0_1/1_1; (iii) 0_2/1_2; and (iv) 0_2/1_2 and0_1/1_1.

Example 14 may include the method of example 9 and/or some otherexamples herein, wherein, if the compact or size-matched DCI format isconfigured for monitoring in a PDCCH CSS, a new higher layer parametermay be used as part of the search space set configuration, that may beconveyed via UE-specific RRC signaling, to indicate whether to monitorfor DCI formats 0_0/1_0 or DCI formats 0_2/1_2 with CRC scrambled withC-RNTI or CS-RNTI or other configurable RNTI.

Example 15 may include the method of example 1 and/or some otherexamples herein, wherein the DCI size budget is extended for UEssupporting DCI formats 0_2/1_2 to maximum of four DCI format sizes forPDCCH with CRC scrambled with C-RNTI or CS-RNTI and one additional DCIformat size for other format/RNTI combination.

Example 16 may include the method of examples 2 or 3 and/or some otherexamples herein, wherein, if the UE is configured to monitor for DCIformats 0_1/1_1 and 0_2/1_2 in a search space set, the DCI format to bemonitored with CRC scrambled with CS-RNTI is additionally indicatedbetween the formats 0_1/1_1 and 0_2/1_2 via a separate higher layerparameter.

Example 17 may include the method of examples 8 or 9 and/or some otherexamples herein, wherein, if the UE is configured to monitor for DCIformats 0_1/1_1 and 0_2/1_2 in a search space set, the DCI format to bemonitored with CRC scrambled with CS-RNTI is the DCI format 0_2/1_2 bydefault.

Example 18 may include the method of examples 8 or 9 and/or some otherexamples herein, wherein when the new format is introduced, the UE canbe configured as part of the search space set configuration inPDCCH-Configuration, to monitor in the UE-SS between non-fallback DCIformats, and new DCI formats.

Example 19 may include the method of examples 8 or 9 and/or some otherexamples herein, wherein the new DCI format introduced, is size-matchedto the existing non-fallback format to avoid introducing a new DCI size,if both versions of non-fallback formats (for example, DCI formats0_1/1_1 and 0_2/1_2) are configured to be monitored in a PDCCH searchspace set.

Example 20 may include the method of example 19 and/or some otherexamples herein, wherein if the UE is expected to monitor for bothnon-fallback DCI formats, and new DCI format, identification betweenthese two formats is defined by introducing new RNTIs for URLLC or a newheader bit field or extending the existing header bit-field that wouldapply to both sets of DCI formats 0_1/1_1 and 0_2/1_2.

Example 21 may include the method of example 19 and/or some otherexamples herein, wherein indication of the DCI format betweennon-fallback and new DCI formats to the UE is done by means of BWPindication field, configuring two BWPs (potentially of samecharacteristics) each associated with one of size-matched DCI formats.The UE monitors only one of the formats in each BWP. The RRCconfiguration then refers to the configured active BWP, meaning thateach of the higher layer configurations are specific to BWP. Once the UEis pointed to a particular BWP, the corresponding RRC configurationreveals the set of enabled features/capabilities for that BWP, and therest of DCI fields are interpreted accordingly.

Example 22 may include the method of example 1 and/or some otherexamples herein, wherein the minimum requirements on BD efforts per slotand the number of CCEs for channel estimation during a slot duration arethe same, irrespective of support and configuration of monitoring ofcompact or size-matched DCI format.

Example 23 may include the method of example 1 and/or some otherexamples herein, wherein, for RIV-based (Type 1 RA) resource allocationusing K-PRB granularity, the value of K is set separately for DL and ULas a new higher layer parameter via UE-specific RRC signaling on aper-BWP (BandWidth Part) basis.

Example 24 may include the method of example 1 and/or some otherexamples herein, wherein, for RIV-based (Type 1 RA) resource allocationusing K-PRB granularity, the value of K is same as the Resource BlockGroup (RBG) size corresponding to RBG Configuration #2 as specified fora given BWP size.

Example 25 may include the method of example 1 and/or some otherexamples herein, wherein, for RIV-based (Type 1 RA) resource allocationusing K-PRB granularity, the value of K is configured to usecorresponding RBG sizes for the BWP from either RBG configuration #1 or#2.

Example 26 may include the method of example 1 and/or some otherexamples herein, wherein, for RIV-based (Type 1 RA) resource allocationusing K-PRB granularity, the indexing of the K-PRB contiguous frequencyresources within a BWP is such that the lowest PRB index of the BWPmarks the first K-PRB set, with the last PRB-set possibly having fewerthan K PRBs.

Example 27 may include the method of example 1 and/or some otherexamples herein, wherein, for RIV-based (Type 1 RA) resource allocationusing K-PRB granularity, the indexing of the K-PRB contiguous frequencyresources within a BWP can be similar to the approach used for indexingof RBGs within a BWP.

Example 28 may include the method of example 1 and/or some otherexamples herein, wherein, for time-domain resource allocation, onlyPDSCH and PUSCH mapping type B may be used for time-domain schedulingwhen using DCI formats 1_2 and 0_2 respectively.

Example 29 may include the method of example 1 and/or some otherexamples herein, wherein, for time-domain resource allocation, onlymapping type B may be used for PUSCH scheduling using DCI format 0_2,but both mapping types A and B are supported for PDSCH when scheduledusing DCI format 1_2.

Example 30 may include the method of example 1 and/or some otherexamples herein, wherein, for time-domain resource allocation, the slotoffset value between PDCCH and scheduled PDSCH, K0, may be indicatedfrom a set of values that is restricted to a lower maximum value thanwhen scheduling using DCI formats 1_0 or 1_1.

Example 31 may include the method of example 1 and/or some otherexamples herein, wherein, for time-domain resource allocation, the slotoffset value between PDCCH and scheduled PUSCH, K2, may be indicatedfrom a set of values that is restricted to a lower maximum value thanwhen scheduling using DCI formats 0_0 or 0_1.

Example 32 may include the method of examples 1, 20, or 21 and/or someother examples herein, wherein, for time-domain resource allocation, theset of possible K0 or K2 values are defined as a function of thesubcarrier spacing (SCS).

Example 33 may include the method of example 1 and/or some otherexamples herein, wherein, for time-domain resource allocation, based onUE-specific configuration of dynamically indicated numbers ofrepetitions of the PDSCH/PUSCH, a field in the scheduling DCI is used todynamically indicate the number of repetitions.

Example 34 may include the method of example 1 and/or some otherexamples herein, wherein, for time-domain resource allocation of PDSCH,instead of explicit indication of the number of repetitions used for thescheduled PDSCH, the information is indicated at least in part based onthe maximum Aggregation Level (AL) or maximum Repetition Level (RL)defined for the search space set where the scheduling PDCCH is detected,or, alternatively, based on the AL or RL used for PDCCH candidate usedto transmit the scheduling DCI.

Example 35 may include the method of example 1 and/or some otherexamples herein, wherein, for Modulation and Coding Scheme (MCS)indication, the MCS field for scheduling PDSCH or PUSCH in a compact orsize-matched DCI format 1_2 or 0_2 respectively and/or in non-fallbackDCI formats 1_1 and 0_1 respectively can be reduced from 5 bit to 4 or 3bit.

Example 36 may include the method of example 35 and/or some otherexamples herein, wherein, the mapping of 32 entries to 16 or 8 entriesrespectively for 4 or 3 bit tables are either predefined or besemi-statically configurable via UE-specific (re)configuration RRCmessage.

Example 37 may include the method of example 35 and/or some otherexamples herein, wherein, the mapping of 5 bit tables to smaller tablesis realized using combinatorial index approach similar to the one usedfor EPDCCH PRB-pair resource set configuration.

Example 38 may include the method of example 1 and/or some otherexamples herein, wherein addition of certain bit-fields are consideredto new DCI formats 0_2/1_2 or DCI formats 0_1/1_1 when configured, toenable different URLLC-related functionalities.

Example 39 may include the method of example 1 and/or some otherexamples herein, wherein DL Pre-emption Indication (PI) is included inDCI formats 1_1 or DCI format 1_2, to indicate whether the current PDSCHassignment may be pre-empted or not.

Example 40 may include a method for new radio (NR) communications, themethod comprising: configuring or causing to configure a UE withmonitoring of PDCCH with monitoring periodicity less than slot duration(PDCCH monitoring case 2), wherein the minimum requirement on the numberof BDs and CCEs per slot is increased compared to Case 1-1 values forthe corresponding subcarrier spacing values, with the constraint thatthe UE is not expected to monitor PDCCH with number of BDs and/or numberof CCEs over any span of ‘p’ consecutive OFDM symbols that is/are largerthan the corresponding values defined for PDCCH monitoring case 1-1 forthe respective SCS values.

Example 41 may include the method of example 40 and/or some otherexamples herein, wherein the value of p is 3.

Example 42 may include the method of example 40 and/or some otherexamples herein, wherein the minimum requirements on BDs and CCEs isdefined on a per-half-slot basis.

Example 43 may include one or more non-transitory, computer-readablemedia having instructions that, when executed, cause a user equipment(UE) in a new radio (NR) system to: transmit, to a base station, anindication of a capability of the UE to support a first downlink controlinformation (DCI) format for Physical Downlink Shared Channel (PDSCH)reception in a downlink (DL) bandwidth part (BWP) and a second DCIformat for scheduling uplink (UL) grants for physical uplink sharedchannel (PUSCH) transmission in a UL bandwidth part (BWP), wherein thefirst DCI format is different from DCI formats 1_0 or 1_1, and thesecond DCI format is different from DCI formats 0_0 or 0_1; determinesearch spaces for monitoring physical downlink control channel (PDCCH)candidates to obtain DCI formats indicated by the base station; monitorthe search spaces for the PDCCH candidates; and detect the indicated DCIformats, wherein the indicated DCI formats are selected from the firstDCI format, the second DCI format, the DCI format 1_0, the DCI format1_1, the DCI format 0_0, or the DCI format 0_1.

Example 44 may include the one or more non-transitory, computer-readablemedia of example 43 and/or some other examples herein, wherein theindicated DCI formats by the base station are selected from the DCIformat 10, the DCI format 1_1, the DCI format 0_0, or the DCI format0_1, and wherein the instructions, when executed, further cause the UEto interpret fields of the indicated DCI formats differently from thefields of the DCI format 1_0, the DCI format 1_1, the DCI format 0_0, orthe DCI format 0_1 as specified in Rel-15 NR specifications based onconfiguration conveyed by a protocol layer.

Example 45 may include the one or more non-transitory, computer-readablemedia of example 43 and/or some other examples herein, wherein theindicated DCI formats includes the first DCI format and the second DCIformat, and wherein the first DCI format and the second DCI format havesmaller sizes than the DCI formats 0_0 and 1_0 for corresponding UL BWPand DL BWP, and wherein the first DCI format and the second DCI formathave a same size.

Example 46 may include the one or more non-transitory, computer-readablemedia of example 43 and/or some other examples herein, wherein the firstDCI format has a same size of the DCI format 0_1, and the second DCIformat has a same size of the DCI format 1_1.

Example 47 may include the one or more non-transitory, computer-readablemedia of example 43 and/or some other examples herein, wherein the firstDCI format or the second DCI format has a field not presented in the DCIformat 1_0, the DCI format 1_1, the DCI format 0_0, or the DCI format0_1.

Example 48 may include the one or more non-transitory, computer-readablemedia of example 43 and/or some other examples herein, wherein the firstDCI format or the second DCI format has a field that is present in theDCI format 1_0, the DCI format 1_1, the DCI format 0_0, or the DCIformat 0_1, and wherein the field in the first DCI format or the secondDCI format is of a smaller size than the field presented in the DCIformat 1_0, the DCI format 1_1, the DCI format 0_0, or the DCI format0_1.

Example 49 may include the one or more non-transitory, computer-readablemedia of example 43 and/or some other examples herein, wherein the firstDCI format or the second DCI format is conveyed to the UE by a PDCCHcandidate that includes an associated cyclic redundancy code (CRC)scrambled with Cell Radio Network Temporary Identifier (C-RNTI),Configured Scheduling (CS)-RNTI, or other configurable RNTI.

Example 50 may include the one or more non-transitory, computer-readablemedia of example 43 and/or some other examples herein, wherein thesearch spaces for monitoring PDCCH candidates includes a UE-specificsearch space (USS) or a common search space (CSS).

Example 51 may include the one or more non-transitory, computer-readablemedia of example 50 and/or some other examples herein, wherein thesearch spaces for monitoring PDCCH candidates are USS, which areconveyed to the UE by a higher layer 2-bit field USS-DCI-format toindicate choice between DCI formats: 0_0, 1_0, 0_1, 1_1, the first DCIformat, or the second DCI format to be monitored.

Example 52 may include the one or more non-transitory, computer-readablemedia of example 43 and/or some other examples herein, wherein the firstDCI format or the second DCI format has a field to indicate a frequencydomain resource assignment or a time domain resource assignment.

Example 53 may include the one or more non-transitory, computer-readablemedia of example 52 and/or some other examples herein, wherein thefrequency domain resource assignment is a Type 1 resource assignmentusing a granularity of K>1 contiguous-in-frequency physical resourceblocks (PRBs).

Example 54 may include the one or more non-transitory, computer-readablemedia of example 53 and/or some other examples herein, wherein the valueof K is given by a resource block group (RBG) size for the correspondingDL or UL BWP respectively according to one of: RBG configuration 1 orRBG configuration 2.

Example 55 may include the one or more non-transitory, computer-readablemedia of example 52 and/or some other examples herein, wherein the timedomain resource assignment only uses PDSCH and PUSCH mapping type B fortime-domain scheduling when using the first DCI format, the second DCIformat respectively.

Example 56 may include the one or more non-transitory, computer-readablemedia of example 43 and/or some other examples herein, wherein the firstDCI format or the second DCI format includes a Modulation and codingscheme (MCS) filed of length 3 or 4 bits for scheduling PDSCH or PUSCH.

Example 57 may include an apparatus for wireless communication,comprising: processing circuitry to: transmit, to a base station in anew radio (NR) system, an indication of a capability of a user equipment(UE) to support a first downlink control information (DCI) format forPhysical Downlink Shared Channel (PDSCH) reception in a downlink (DL)bandwidth part (BWP) and a second DCI format for scheduling uplink (UL)grants for physical uplink shared channel (PUSCH) transmission in a ULbandwidth part (BWP), wherein the first DCI format is different from DCIformats 1_0 or 1_1, and the second DCI format is different from DCIformats 0_0 or 0_1; determine search spaces for monitoring physicaldownlink control channel (PDCCH) candidates to obtain DCI formatsindicated by the base station; monitor the search spaces for the PDCCHcandidates; and detect the indicated DCI formats, wherein the indicatedDCI formats are selected from the first DCI format, the second DCIformat, the DCI format 1_0, the DCI format 1_1, the DCI format 0_0, orthe DCI format 0_1; and memory circuitry coupled to the processingcircuitry, the memory circuitry to store the indicated DCI formats.

Example 58 may include the apparatus of example 57 and/or some otherexamples herein, wherein the indicated DCI formats by the base stationare selected from the DCI format 1_0, the DCI format 1_1, the DCI format0_0, or the DCI format 0_1, and wherein the processing circuitry is tointerpret fields of the indicated DCI formats differently from thefields of the DCI format 1_0, the DCI format 1_1, the DCI format 0_0, orthe DCI format 0_1 as specified in Rel-15 NR specifications based onconfiguration conveyed by a protocol layer.

Example 59 may include the apparatus of example 57 and/or some otherexamples herein, wherein the indicated DCI formats includes the firstDCI format and the second DCI format, and wherein the first DCI formatand the second DCI format have smaller sizes than the DCI formats 0_0and 1_0 for corresponding UL BWP and DL BWP, and wherein the first DCIformat and the second DCI format have a same size.

Example 60 may include the apparatus of example 57 and/or some otherexamples herein, wherein the first DCI format has a same size of the DCIformat 0_1, and the second DCI format has a same size of the DCI format1_1.

Example 61 may include the apparatus of example 57 and/or some otherexamples herein, wherein the first DCI format or the second DCI formathas a field not presented in the DCI format 1_0, the DCI format 1_1, theDCI format 0_0, or the DCI format 0_1.

Example 62 may include the apparatus of example 57 and/or some otherexamples herein, wherein the search spaces for monitoring PDCCHcandidates includes a UE-specific search space (USS) or a common searchspace (CSS).

Example 63 may include the apparatus of example 62 and/or some otherexamples herein, wherein the search spaces for monitoring PDCCHcandidates are USS, which are conveyed to the UE by a higher layer 2-bitfield USS-DCI-format to indicate choice between DCI formats: 0_0, 1_0,0_1, 1_1, the first DCI format, or the second DCI format to bemonitored.

Example 64 may include one or more non-transitory, computer-readablemedia having instructions that, when executed, cause a base station in anew radio (NR) system to: receive or cause to receive, an indication ofa capability of a user equipment (UE) to support a first downlinkcontrol information (DCI) format for Physical Downlink Shared Channel(PDSCH) reception in a downlink (DL) bandwidth part (BWP) and a secondDCI format for scheduling uplink (UL) grants for physical uplink sharedchannel (PUSCH) transmission in a UL bandwidth part (BWP), wherein thefirst DCI format is different from DCI formats 1_0 or 1_1, and thesecond DCI format is different from DCI formats 0_0 or 0_1; determinesearch spaces for the UE to monitor physical downlink control channel(PDCCH) candidates to obtain DCI formats indicated by the base station;and select a DCI formats from the first DCI format, the second DCIformat, the DCI format 1_0, the DCI format 1_1, the DCI format 0_0, orthe DCI format 0_1, the DCI formats to be indicated to the UE; andtransmit, to the UE, the selected DCI formats.

Example 65 may include the one or more non-transitory, computer-readablemedia of example 64 and/or some other examples herein, wherein theselected DCI formats are transmitted to the UE by a PDCCH candidate thatincludes an associated cyclic redundancy code (CRC) scrambled with CellRadio Network Temporary Identifier (C-RNTI), Configured Scheduling(CS)-RNTI, or other configurable RNTI.

Example 66 may include the one or more non-transitory, computer-readablemedia of example 65 and/or some other examples herein, wherein thesearch spaces for monitoring PDCCH candidates are UE-specific searchspace (USS), which are conveyed to the UE by a higher layer 2-bit fieldUSS-DCI-format to indicate choice between DCI formats: 0_0, 1_0, 0_1,1_1, the first DCI format, or the second DCI format to be monitored.

Example 67 may include the one or more non-transitory, computer-readablemedia of example 64 and/or some other examples herein, wherein the firstDCI format or the second DCI format has a field to indicate a frequencydomain resource assignment or a time domain resource assignment.

Example 68 may include an apparatus comprising means to perform one ormore elements of a method described in or related to any of examples1-67, or any other method or process described herein.

Example 69 may include one or more non-transitory computer-readablemedia comprising instructions to cause an electronic device, uponexecution of the instructions by one or more processors of theelectronic device, to perform one or more elements of a method describedin or related to any of examples 1-67, or any other method or processdescribed herein.

Example 70 may include an apparatus comprising logic, modules, orcircuitry to perform one or more elements of a method described in orrelated to any of examples 1-67, or any other method or processdescribed herein.

Example 71 may include a method, technique, or process as described inor related to any of examples 1-67, or portions or parts thereof.

Example 72 may include an apparatus comprising: one or more processorsand one or more computer readable media comprising instructions that,when executed by the one or more processors, cause the one or moreprocessors to perform the method, techniques, or process as described inor related to any of examples 1-67, or portions thereof.

Example 73 may include a signal as described in or related to any ofexamples 1-67, or portions or parts thereof.

Example 74 may include a signal in a wireless network as shown anddescribed herein.

Example 75 may include a method of communicating in a wireless networkas shown and described herein.

Example 76 may include a system for providing wireless communication asshown and described herein.

Example 77 may include a device for providing wireless communication asshown and described herein.

Any of the above described examples may be combined with any otherexample (or combination of examples), unless explicitly statedotherwise. The foregoing description of one or more implementationsprovides illustration and description, but is not intended to beexhaustive or to limit the scope of embodiments to the precise formdisclosed. Modifications and variations are possible in light of theabove teachings or may be acquired from practice of various embodiments.

What is claimed is:
 1. One or more non-transitory, computer-readablemedia having instructions that, when executed, cause a user equipment(UE) in a new radio (NR) system to: transmit, to a base station, anindication of a capability of the UE to support a first downlink controlinformation (DCI) format for Physical Downlink Shared Channel (PDSCH)reception in a downlink (DL) bandwidth part (BWP) and a second DCIformat for scheduling uplink (UL) grants for physical uplink sharedchannel (PUSCH) transmission in a UL bandwidth part (BWP), wherein thefirst DCI format for the DL BWP is different from DCI formats 1_0 and1_1, and the second DCI format for the UL BWP is different from DCIformats 0_0 and 0_1; determine search spaces for monitoring physicaldownlink control channel (PDCCH) candidates to obtain DCI formatsindicated by the base station; monitor the search spaces for the PDCCHcandidates; and detect the indicated DCI formats, wherein the indicatedDCI formats are selected from the first DCI format, the second DCIformat, the DCI format 1_0, the DCI format 1_1, the DCI format 0_0, orthe DCI format 0_1.
 2. The one or more non-transitory, computer-readablemedia of claim 1, wherein the indicated DCI formats by the base stationare selected from the DCI format 1_0, the DCI format 1_1, the DCI format0_0, or the DCI format 0_1, and wherein the instructions, when executed,further cause the UE to interpret fields of the indicated DCI formatsdifferently from fields of the DCI format 1_0, the DCI format 1_1, theDCI format 0_0, or the DCI format 0_1 as specified in Rel-15 NRspecifications based on configuration conveyed by a protocol layer. 3.The one or more non-transitory, computer-readable media of claim 1,wherein the indicated DCI formats include the first DCI format and thesecond DCI format, and wherein the first DCI format and the second DCIformat have smaller sizes than the DCI formats 0_0 and 1_0 forcorresponding UL BWP and DL BWP, and wherein the first DCI format andthe second DCI format have a same size.
 4. The one or morenon-transitory, computer-readable media of claim 1, wherein the firstDCI format has a same size of the DCI format 0_1, and the second DCIformat has a same size of the DCI format 1_1.
 5. The one or morenon-transitory, computer-readable media of claim 1, wherein the firstDCI format or the second DCI format has a field not presented in the DCIformat 1_0, the DCI format 1_1, the DCI format 0_0, or the DCI format0_1.
 6. The one or more non-transitory, computer-readable media of claim1, wherein the first DCI format or the second DCI format has a fieldthat is presented in the DCI format 1_0, the DCI format 1_1, the DCIformat 0_0, or the DCI format 0_1, and wherein the field in the firstDCI format or the second DCI format is of a smaller size than the fieldpresented in the DCI format 1_0, the DCI format 1_1, the DCI format 0_0,or the DCI format 0_1.
 7. The one or more non-transitory,computer-readable media of claim 1, wherein the first DCI format or thesecond DCI format is conveyed to the UE by a PDCCH candidate thatincludes an associated cyclic redundancy code (CRC) scrambled with aCell Radio Network Temporary Identifier (C-RNTI), Configured Scheduling(CS)-RNTI, or other configurable RNTI.
 8. The one or morenon-transitory, computer-readable media of claim 1, wherein the searchspaces for monitoring the PDCCH candidates includes a UE-specific searchspace (USS) or a common search space (CSS).
 9. The one or morenon-transitory, computer-readable media of claim 8, wherein the searchspaces for monitoring the PDCCH candidates are USS, which are conveyedto the UE by a higher layer 2-bit field USS-DCI-format to indicatechoice between DCI formats: 0_0, 1_0, 0_1, 1_1, the first DCI format, orthe second DCI format to be monitored.
 10. The one or morenon-transitory, computer-readable media of claim 1, wherein the firstDCI format or the second DCI format has a field to indicate a frequencydomain resource assignment or a time domain resource assignment.
 11. Theone or more non-transitory, computer-readable media of claim 10, whereinthe frequency domain resource assignment is a Type 1 resource assignmentusing a granularity of K>1 contiguous-in-frequency physical resourceblocks (PRBs).
 12. The one or more non-transitory, computer-readablemedia of claim 11, wherein the value of K is given by a resource blockgroup (RBG) size for the corresponding DL or UL BWP respectivelyaccording to one of: RBG configuration 1 or RBG configuration
 2. 13. Theone or more non-transitory, computer-readable media of claim 10, whereinthe time domain resource assignment only uses PDSCH and PUSCH mappingtype B for time-domain scheduling when using the first DCI format, orthe second DCI format respectively.
 14. The one or more non-transitory,computer-readable media of claim 1, wherein the first DCI format or thesecond DCI format includes a Modulation and coding scheme (MCS) filed oflength 3 or 4 bits for scheduling PDSCH or PUSCH.
 15. An apparatus forwireless communication, comprising: processing circuitry to: transmit,to a base station in a new radio (NR) system, an indication of acapability of a user equipment (UE) to support a first downlink controlinformation (DCI) format for Physical Downlink Shared Channel (PDSCH)reception in a downlink (DL) bandwidth part (BWP) and a second DCIformat for scheduling uplink (UL) grants for physical uplink sharedchannel (PUSCH) transmission in a UL bandwidth part (BWP), wherein thefirst DCI format for the DL BWP is different from DCI formats 1_0 and1_1, and the second DCI format for the UL BWP is different from DCIformats 0_0 and 0_1; determine search spaces for monitoring physicaldownlink control channel (PDCCH) candidates to obtain DCI formatsindicated by the base station; monitor the search spaces for the PDCCHcandidates; and detect the indicated DCI formats, wherein the indicatedDCI formats are selected from the first DCI format, the second DCIformat, the DCI format 1_0, the DCI format 1_1, the DCI format 0_0, orthe DCI format 0_1; and memory circuitry coupled to the processingcircuitry, the memory circuitry to store the indicated DCI formats. 16.The apparatus of claim 15, wherein the indicated DCI formats by the basestation are selected from the DCI format 1_0, the DCI format 1_1, theDCI format 0_0, or the DCI format 0_1, and wherein the processingcircuitry is to interpret fields of the indicated DCI formatsdifferently from fields of the DCI format 1_0, the DCI format 1_1, theDCI format 0_0, or the DCI format 0_1 as specified in Rel-15 NRspecifications based on configuration conveyed by a protocol layer. 17.The apparatus of claim 15, wherein the indicated DCI formats include thefirst DCI format and the second DCI format, and wherein the first DCIformat and the second DCI format have smaller sizes than the DCI formats0_0 and 1_0 for corresponding UL BWP and DL BWP, and wherein the firstDCI format and the second DCI format have a same size.
 18. The apparatusof claim 15, wherein the first DCI format has a same size of the DCIformat 0_1, and the second DCI format has a same size of the DCI format1_1.
 19. The apparatus of claim 15, wherein the first DCI format or thesecond DCI format has a field not presented in the DCI format 1_0, theDCI format 1_1, the DCI format 0_0, or the DCI format 0_1.
 20. Theapparatus of claim 15, wherein the search spaces for monitoring thePDCCH candidates includes a UE-specific search space (USS) or a commonsearch space (CSS).
 21. The apparatus of claim 20, wherein the searchspaces for monitoring the PDCCH candidates are USS, which are conveyedto the UE by a higher layer 2-bit field USS-DCI-format to indicate achoice between DCI formats: 0_0, 1_0, 0_1, 1_1, the first DCI format, orthe second DCI format to be monitored.
 22. One or more non-transitory,computer-readable media having instructions that, when executed, cause abase station in a new radio (NR) system to: receive or cause to receive,an indication of a capability of a user equipment (UE) to support afirst downlink control information (DCI) format for Physical DownlinkShared Channel (PDSCH) reception in a downlink (DL) bandwidth part (BWP)and a second DCI format for scheduling uplink (UL) grants for physicaluplink shared channel (PUSCH) transmission in a UL bandwidth part (BWP),wherein the first DCI format for the DL BWP is different from DCIformats 1_0 and 1_1, and the second DCI format for the UL BWP isdifferent from DCI formats 0_0 and 0_1; determine search spaces for theUE to monitor physical downlink control channel (PDCCH) candidates toobtain DCI formats indicated by the base station; select DCI formatsfrom the first DCI format, the second DCI format, the DCI format 1_0,the DCI format 1_1, the DCI format 0_0, or the DCI format 0_1, the DCIformats to be indicated to the UE; and transmit, to the UE, the selectedDCI formats.
 23. The one or more non-transitory, computer-readable mediaof claim 22, wherein the selected DCI formats are transmitted to the UEby a PDCCH candidate that includes an associated cyclic redundancy code(CRC) scrambled with a Cell Radio Network Temporary Identifier (C-RNTI),Configured Scheduling (CS)-RNTI, or other configurable RNTI.
 24. The oneor more non-transitory, computer-readable media of claim 23, wherein thesearch spaces for monitoring the PDCCH candidates are UE-specific searchspace (USS), which are conveyed to the UE by a higher layer 2-bit fieldUSS-DCI-format to indicate a choice between DCI formats: 0_0, 1_0, 0_1,1_1, the first DCI format, or the second DCI format to be monitored. 25.The one or more non-transitory, computer-readable media of claim 22,wherein the first DCI format or the second DCI format has a field toindicate a frequency domain resource assignment or a time domainresource assignment.